diff --git a/Test-Management/installation.md b/Test-Management/installation.md
index b7ef4c00ef1ec7d01157a0d776a6900282e80a20..24dceb4702a1b1f5994807eb3170c3029e1bf8b4 100755
--- a/Test-Management/installation.md
+++ b/Test-Management/installation.md
@@ -3,8 +3,8 @@ title:  Installation manual
 subtitle: Gazelle Test Management
 author: Nicolas BAILLIET
 function: Engineer
-releasedate: 13/04/2021
-toolversion: 5.14.x
+releasedate: 18/05/2021
+toolversion: 5.15.x
 version: 1.02
 status: Approved document
 reference: KER1-MAN-IHE-TEST_MANAGEMENT_INSTALLATION-1_02
@@ -110,6 +110,26 @@ Copy the gazelle-tm.ear into the " standalone\\deployments" directory of your JB
 
 # Configuration
 
+## SSO
+
+With the release 5.15.0, Gazelle Test Management  needs a file to interact with the SSO application.
+This application read the configuration of the SSO in a file located in `/opt/gazelle/cas`. We need to create this folder and the configuration file `EVSClient.properties`.
+
+```
+ mkdir /opt/gazelle/cas
+ touch /opt/gazelle/cas/EVSClient.properties
+ chown -R jboss:jboss-admin /opt/gazelle/cas
+ chmod -R g+w /opt/gazelle/cas
+```
+The file **gazelle-tm.properties** has shall be created and save in **/opt/gazelle/cas**.
+
+The file shall contain the following statements :
+- casServerUrlPrefix = https://yourUrl.com/sso
+- casServerLoginUrl = https://yourUrl.com/sso/login
+- casLogoutUrl = https://yourUrl.com/sso/logout
+- service = https://yourUrl.com/gazelle
+
+
 This instance of Test Management you have just deployed is free of organization, user and testing session. Consequently, the next step will be to create your organization, your account (as an administrator of the application) and the testing session. A testing session is used to hold one event, for example a Connectathon, a showcase or whatever requiring the use of Test Management. If the first part of the installation is successful, you should see the Gazelle home page (see file entitled Home page before installation).
 
 ![](./media/TM_first_install.png)
diff --git a/Test-Management/release-note.md b/Test-Management/release-note.md
index 5228a605e81d9a2f9dd8dd2c4ceb3ff9004c1ec6..164475bd1b7c89301d282258a5a7d4dbd815e800 100644
--- a/Test-Management/release-note.md
+++ b/Test-Management/release-note.md
@@ -8,6 +8,34 @@ function: Software Engineer
 customer: IHE Europe
 reference: KER1-RNO-IHE-TEST_MANAGEMENT
 ---
+
+# 5.15.0
+
+_Release date: 2021-05-18_
+
+__Warning__ : this release 
+
+__Story__
+* \[[GZL-4953](https://gazelle.ihe.net/jira/browse/GZL-4953)\] - Sending notifications by emails
+* \[[GZL-4954](https://gazelle.ihe.net/jira/browse/GZL-4954)\] - Vendors may be able to set any status in a test instance
+
+
+__Improvement__
+* \[[GZL-4952](https://gazelle.ihe.net/jira/browse/GZL-4952)\] - Privacy of the sample section in Gazelle
+* \[[GZL-4955](https://gazelle.ihe.net/jira/browse/GZL-4955)\] - Update cas configuration to use a dedicated property file
+
+
+
+
+## Gazelle model 4.2.7
+
+__Story__
+* \[[GZL-4953](https://gazelle.ihe.net/jira/browse/GZL-4953)\] - Sending notifications by emails
+
+__Bug__
+
+* \[[GZL-4967](https://gazelle.ihe.net/jira/browse/GZL-4967)\] "Comment" tab of a system shall not be disclosed to users that are not part of the company owning the system
+
 # 5.14.3
 _Release date: 2021-05-06_
 
diff --git a/Test-Management/user.md b/Test-Management/user.md
index 438008f54b69264bc4f865ba39842bd3501fdc58..dceea61581a4c11f04648fc6db87f46326fae8a6 100644
--- a/Test-Management/user.md
+++ b/Test-Management/user.md
@@ -3,8 +3,8 @@ title:  User manual
 subtitle: Gazelle Test Management
 author: Guillaume THOMAZON
 function: Engineer
-releasedate: 30/10/2019
-toolversion: 5.14.x
+releasedate: 18/05/2021
+toolversion: 5.15.x
 version: 2.01
 status: To be verified
 reference: KER1-MAN-IHE-TEST_MANAGEMENT_USER-2_01
@@ -2029,6 +2029,7 @@ This permanent link has this form :
 *  system : the keyword of the system
 *  testingSessionId : the id of the testing session (15 for pisa, 8 for Bordeaux, etc).
 
+
 # TM - Release notes
 
 Gazelle Test Management release notes can be found on the JIRA pages of the project at the following URL :