diff --git a/Gazelle-Master-Model/user.md b/Gazelle-Master-Model/user.md
index b632a3b4144a0c809fa08adcefa9191b9b7c4ef6..3a33c3ea99f3e6e67614de7860b0c519ac414bd7 100755
--- a/Gazelle-Master-Model/user.md
+++ b/Gazelle-Master-Model/user.md
@@ -213,6 +213,7 @@ It gives general informations about the test:
 * The **peer type** indicates is the test is of type "No peer", "Peer to Peer" or "Group Test"
 * The **permanent link** to the test is printed in this part (computed by Gazelle)
 * The **version** of the test gives an indication of the most recent testing event for which the test was created/modified.
+* The **Is CTT** attribute indicates whether the test integrates or not a CTT result. 
 * The **Is orchestrable** attribute indicates whether the test will be run against a simulator (true) or against another system under test (false). When run against a simulator, the test requires the use of Bpel service and Gazelle web services to be orchestrated. Those services will enable the simulator to communicate with Gazelle in a standalone mode without any help from somebody.
 * The **Is validated** attribute indicates whether the test is validated or not, it's mostly used in the context of accredited testing
 
@@ -265,6 +266,22 @@ Once you have chosen the roles involved in your test, you will be asked, for eac
 * **Card Max**: (cardinality) how many (at most) systems with this role can be involved in the test
 * **Optionality**: Require means that the test is required for that Role Optional means that the test is optional for that role.
 
+## CTT Result
+
+To help integrate CTT result from the CTT tool, an improvement has been done to allow a vendor to upload on Gazelle Test Management the CTT report. 
+An uploading Rest Api is integrated in order to save the report to the test instance. 
+
+### CTT Token 
+![](./media/TokenProvider.png)
+When the "Is CTT" attribute is set, a token provider appears on the test instance page. It creates a unique token value referring to the test instance.
+
+### CTT API
+
+In order to upload a file on a CTT Test Instance, the user needs to provide to the webservice the token value of the Test Instance. 
+
+Once the file is uploaded, the status of the Test instance wiil be set to "To be verified" and a message will be sent to the monitor. 
+
+   
 ## Test Steps
 
 To help vendors with performing the test, we cut the test into small entities called test steps. In a newly defined test, when you first arrive on this page, you will find a sequence diagram only filled with the different roles you have previously defined. As you add test steps, you will be able to see the sequence diagram is automatically updated according to the steps you have defined. The red arrows stand for secured transaction (TLS set to true)