GITBOOK-456: No subject

Author: adnan-kamili

README.md

@@ -1,28 +1,30 @@
 # Welcome to Cryptlex!
 
-Cryptlex lets you license your software apps effortlessly. You can easily generate license keys using our [REST API](https://api.cryptlex.com/v3/docs) or through the [dashboard](https://app.cryptlex.com/) and validate the license keys in your software apps using [LexActivator](https://docs.cryptlex.com/node-locked-licenses/overview) \(Cryptlex client library\). 
+Cryptlex lets you license your software apps effortlessly. You can easily generate license keys using our [REST API](https://api.cryptlex.com/v3/docs) or through the [admin portal](https://app.cryptlex.com) and validate the license keys in your software apps using [LexActivator](https://docs.cryptlex.com/node-locked-licenses/overview) (Cryptlex client library). 
 
-The license keys can't be shared by your customers because they are node-locked \(locked to the machine where they are activated\), hence preventing casual piracy.
+The license keys can't be shared by your customers because they are node-locked (locked to the machine where they are activated), hence preventing casual piracy.
 
 ## Quick start
 
 The complete process of adding licensing to your software app has three steps:
 
 ### Step 1. Add a product in Cryptlex
 
-Log in to the Cryptlex [dashboard](https://app.cryptlex.com/). Click the "Products" link in the sidebar and add your first product. You will need to create a default [license policy](https://docs.cryptlex.com/license-management/license-policies) too for the product. After creating the product select the "Licenses" link in the products table and create your first license key.
+Log in to the Cryptlex [admin portal](https://app.cryptlex.com). Click the `Home -> Products` link in the sidebar and add your first product. You will need to create a default [license template](license-management/license-templates.md) too for the product. After creating the product click the `Licenses` link in the sidebar and create your first license.
 
 ### Step 2. Adding LexActivator to your software app
 
-LexActivator is the Cryptlex client library which you will use to add licensing to your product. Using this library you can easily validate the license key in your software app. It is a shared library available for all the major platforms - Windows, macOS, and Linux. The library can be used with almost all programming languages. To learn more refer to:
+LexActivator is the Cryptlex client library which you will use to add licensing to your product. Using this library you can easily validate the license key in your software app. It is a shared library available for all the major platforms - Windows, macOS and Linux. The library can be used with almost all programming languages. To learn more refer to:
 
-{% page-ref page="node-locked-licenses/using-lexactivator/" %}
+{% content-ref url="node-locked-licenses/using-lexactivator/" %}
+[using-lexactivator](node-locked-licenses/using-lexactivator/)
+{% endcontent-ref %}
 
 ### Step 3. Using Cryptlex Web API to automate the order process
 
-You can use the [web API](https://api.cryptlex.com/v3/docs) to automate your order processes by generating new license keys when an order is processed through your payment processor. The web API can be used with any payment processor to generate license keys when an order is processed. To learn more refer to:
-
-{% page-ref page="web-integration/" %}
-
+You can use the [web API](https://api.cryptlex.com/v3/docs) to automate your order processes by generating new licenses when an order is processed through your payment processor. The web API can be used with any payment processor to generate licenses when an order is processed. To learn more refer to:
 
+{% content-ref url="web-integration/" %}
+[web-integration](web-integration/)
+{% endcontent-ref %}
 

SUMMARY.md

@@ -5,7 +5,7 @@
   * [Overview](getting-started/overview.md)
   * [Licensing Models](getting-started/licensing-models.md)
 * [License Management](license-management/README.md)
-  * [License Policies](license-management/license-policies.md)
+  * [License Templates](license-management/license-templates.md)
   * [Implementing License Models](license-management/implementing-license-models.md)
   * [Custom License Fields](license-management/custom-license-fields.md)
   * [Meter Attributes](license-management/meter-attributes.md)
@@ -35,7 +35,7 @@
 * [Node Locked Licenses](node-locked-licenses/README.md)
   * [Overview](node-locked-licenses/overview.md)
   * [Using LexActivator](node-locked-licenses/using-lexactivator/README.md)
-    * [Using LexActivator with C, C++ & Objective C](node-locked-licenses/using-lexactivator/using-lexactivator-with-c-c++-and-objective-c.md)
+    * [Using LexActivator with C, C++ and Objective C](node-locked-licenses/using-lexactivator/using-lexactivator-with-c-c++-and-objective-c.md)
     * [Using LexActivator with C#](node-locked-licenses/using-lexactivator/using-lexactivator-with-csharp.md)
     * [Using LexActivator with VB.NET](node-locked-licenses/using-lexactivator/using-lexactivator-with-vb.net.md)
     * [Using LexActivator with Java](node-locked-licenses/using-lexactivator/using-lexactivator-with-java.md)

automated-emails.md

@@ -17,7 +17,7 @@ Automated emails can be used to automatically send emails to your customers when
 
 ## Creating an automated email
 
-You can easily create an automated email through the dashboard. Go to the [automated emails](https://app.cryptlex.com/automated-emails) section in the dashboard and click the add button. An automated email form with the following fields will popup: 
+You can easily create an automated email through the admin portal. Go to the `Developer -> Automated Emails` section in the admin portal and click the add button. An automated email form with the following fields will popup: 
 
 {% hint style="info" %}
 After creating the automated email, make sure you link it with the product.
@@ -131,20 +131,19 @@ For other supported filters please refer to the following:
 
 ## Sending test emails
 
-After you have created the automated email, click the automated email in the automated emails table. On the automated email page, you will find a **`Send Test Email`** button on the right top. You can use this to test your automated email by providing the sample data.
+After you have created the automated email, click the  **`Send Test Email`** option in the actions menu in the table. You can use this to test your automated email.
 
 ## Verifying email domain
 
-In order for Cryptlex to send emails on your behalf using your **From Email** address, you must verify that you own the domain. This is done by adding a Sending Domain in Cryptlex and verifying the  DNS records shown in the Sending Domain.
+For Cryptlex to send emails on your behalf using your **From Email** address, you must verify that you own the domain. This is done by adding a Sending Domain in Cryptlex and verifying the  DNS records shown in the Sending Domain.
 
-If you don’t add the domain verification records, Cryptlex sends emails using **[email protected]** email address. If you want to give your customers a white-label experience, hiding all Cryptlex branding, you must add and verify the sending domain.
+If you don’t add the domain verification records, Cryptlex sends emails using `noreply@cryptlex-mail.com` email address. If you want to give your customers a white-label experience, hiding all Cryptlex branding, you must add and verify the sending domain.
 
 ### **To verify that a domain belongs to you**
 
-1. On the automated emails page in the dashboard, click on the **`Sending Domains`** button.
-2. On the Sending Domains page click on the **`Add`** button to add your domain.
-3. Verify the domain by adding the required TXT and CNAME DNS entries. 
-4. After you have added the CNAME and TXT records, click the **`Verify`** button to confirm that all of your records are now valid.
+1. On the `Settings -> Customizations` page in the admin portal, click on the **`Add`** button in the `Email Sending Domain` section to add your domain.
+2. Verify the domain by adding the required TXT and CNAME DNS entries. 
+3. After you have added the CNAME and TXT records, click the **`Verify`** button to confirm that all of your records are now valid.
 
 After your domain is verified, leave the CNAME and TXT records in place.
 

feature-management/creating-product-versions.md

@@ -1,12 +1,22 @@
 # Creating Product Versions
 
-## Using the Dashboard
+## Using the Admin Portal
 
-After you have created a `Product`, within your Product Page, there is a button labelled Product Versions which will lead you to a page where you can create `Product Versions` for that particular `Product`. Before creating `Product Versions`, you must create `Feature Flags` by navigating via the following route:
+After creating a product, follow these steps to create product versions:
 
-> (Dashboard Home > Products > ProductA > Product Versions > Feature Flags)
+### 1. Create feature flags:
 
-The values of each flag can then be set when creating `Product Versions`. `Feature Flags`  created later will automatically reflect in all `Product Versions` with no data and are disabled by default. You can then update your product versions and set the value of the feature flag as required.
+• Navigate to the Feature Flags page by going to `Features -> Feature Flags` in the sidebar.
+
+• Create all necessary feature flags for your product.
+
+### 2. Create product versions:
+
+• Navigate to the Product Versions page by going to `Features -> Product Versions` in the sidebar.
+
+• Create product versions for your product.
+
+The values of each feature flag can be set when creating product versions. Any feature flags created later will automatically appear in all product versions but will be disabled by default. You can then update your product versions and set the value of each feature flag as required.
 
 ## Accessing feature flags in your application
 

floating-licenses/on-premise-floating-licenses/lexfloatserver.md

@@ -12,9 +12,9 @@ LexFloatServer has [`VS2015 runtime`](https://www.microsoft.com/en-in/download/d
 
 LexFloatServer can be downloaded from the downloads page in the dashboard. Simply login to your Cryptlex account and download LexFloatServer binary for Windows, macOS or Linux:
 
-* ​[Download LexFloatServer for Windows](https://app.cryptlex.com/downloads)​
-* [​Download LexFloatServer for macOS](https://app.cryptlex.com/downloads)
-* ​[Download LexFloatServer for Linux](https://app.cryptlex.com/downloads)​
+* ​[Download LexFloatServer for Windows](https://app.cryptlex.com/developer/sdk-downloads)​
+* [​Download LexFloatServer for macOS](https://app.cryptlex.com/developer/sdk-downloads)
+* ​[Download LexFloatServer for Linux](https://app.cryptlex.com/developer/sdk-downloads)​
 
 ## Configuring the LexFloatServer
 
@@ -84,97 +84,94 @@ LexFloatServer exposes a few API endpoints which can also be used to activate th
 
 Send a POST request to the **/api/server/activate** API endpoint with a JSON request body containing the license key and optionally the activation metadata.
 
-{% swagger baseUrl="http://localhost:8090" path="/api/server/activate" method="post" summary="Activate server" %}
-{% swagger-description %}
+## Activate server
 
-{% endswagger-description %}
+<mark style="color:green;">`POST`</mark> `http://localhost:8090/api/server/activate`
 
-{% swagger-parameter in="body" name="licenseKey" type="string" %}
-License key to activate the server.
-{% endswagger-parameter %}
+#### Request Body
 
-{% swagger-parameter in="body" name="metadata" type="array" %}
-Activation metadata.
-{% endswagger-parameter %}
+| Name       | Type   | Description                         |
+| ---------- | ------ | ----------------------------------- |
+| licenseKey | string | License key to activate the server. |
+| metadata   | array  | Activation metadata.                |
 
-{% swagger-response status="200" description="" %}
+{% tabs %}
+{% tab title="200 " %}
 ```javascript
 {
   "message": "Server license activation successful!",
   "code": "SERVER_LICENSE_ACTIVATED"
 }
 ```
-{% endswagger-response %}
+{% endtab %}
 
-{% swagger-response status="400" description="" %}
+{% tab title="400 " %}
 ```javascript
 {
   "message": "Server license activation failed!",
   "code": "SERVER_INVALID_LICENSE_KEY"
 }
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 #### Offline activation
 
 Send a POST request to the **/api/server/offline-activation-request** API endpoint with a JSON request body containing the license key and optionally the activation metadata.
 
-{% swagger baseUrl="http://localhost:8090" path="/api/server/offline-activation-request" method="post" summary="Generate offline activation request" %}
-{% swagger-description %}
+## Generate offline activation request
 
-{% endswagger-description %}
+<mark style="color:green;">`POST`</mark> `http://localhost:8090/api/server/offline-activation-request`
 
-{% swagger-parameter in="body" name="licenseKey" type="string" %}
-License key to activate the server.
-{% endswagger-parameter %}
+#### Request Body
 
-{% swagger-parameter in="body" name="metadata" type="array" %}
-Activation metadata.
-{% endswagger-parameter %}
+| Name       | Type   | Description                         |
+| ---------- | ------ | ----------------------------------- |
+| licenseKey | string | License key to activate the server. |
+| metadata   | array  | Activation metadata.                |
 
-{% swagger-response status="200" description="" %}
+{% tabs %}
+{% tab title="200 " %}
 ```javascript
 {
   "offlineRequest": "U7l69tNy8..."
 }
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 After generating the offline response from the admin dashboard, send a POST request to the **/api/server/offline-activate** API endpoint with a JSON request body containing the license key and the offline response.
 
-{% swagger baseUrl="http://localhost:8090" path="/api/server/offline-activate" method="post" summary="Activate server offline" %}
-{% swagger-description %}
+## Activate server offline
 
-{% endswagger-description %}
+<mark style="color:green;">`POST`</mark> `http://localhost:8090/api/server/offline-activate`
 
-{% swagger-parameter in="body" name="licenseKey" type="string" %}
-License key to activate the server.
-{% endswagger-parameter %}
+#### Request Body
 
-{% swagger-parameter in="body" name="offlineResponse" type="string" %}
-Offline activation response.
-{% endswagger-parameter %}
+| Name            | Type   | Description                         |
+| --------------- | ------ | ----------------------------------- |
+| licenseKey      | string | License key to activate the server. |
+| offlineResponse | string | Offline activation response.        |
 
-{% swagger-response status="200" description="" %}
+{% tabs %}
+{% tab title="200 " %}
 ```javascript
 {
   "message": "Server offline license activation successful!",
   "code": "SERVER_LICENSE_ACTIVATED"
 }
 ```
-{% endswagger-response %}
+{% endtab %}
 
-{% swagger-response status="400" description="" %}
+{% tab title="400 " %}
 ```javascript
 {
   "message": "Server offline license activation failed!",
   "code": "SERVER_INVALID_LICENSE_KEY"
 
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 ## Installing LexFloatServer on Windows
 
@@ -264,12 +261,14 @@ lexfloatserver -u --service-name com.mycompany.myfloatingserver
 
 LexFloatServer exposes a stats API endpoint that can be used to get the current stats of the server.
 
-{% swagger baseUrl="http://localhost:8090" path="/api/server/stats" method="get" summary="Gets the server stats" %}
-{% swagger-description %}
+## Gets the server stats
+
+<mark style="color:blue;">`GET`</mark> `http://localhost:8090/api/server/stats`
+
 Gets the current server stats
-{% endswagger-description %}
 
-{% swagger-response status="200" description="" %}
+{% tabs %}
+{% tab title="200 " %}
 ```javascript
 {
   "leaseDuration": 1800,
@@ -282,19 +281,21 @@ Gets the current server stats
   "serverSyncGracePeriodExpiryDate": 1580739313
 }
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 ## Getting server license info
 
 LexFloatServer exposes a license info API endpoint that can be used to get the information related to the license used to activate the LexFloatServer.
 
-{% swagger method="get" path="/api/server/license-info" baseUrl="http://localhost:8090" summary="Gets the license info" %}
-{% swagger-description %}
+## Gets the license info
+
+<mark style="color:blue;">`GET`</mark> `http://localhost:8090/api/server/license-info`
+
 Gets the license info of the license used to activate the LexFloatServer
-{% endswagger-description %}
 
-{% swagger-response status="200: OK" description="" %}
+{% tabs %}
+{% tab title="200: OK " %}
 ```javascript
 {
   "key": "280D2B-B48A03-406BBC-2EEE4A-C20FB3-749630",
@@ -315,19 +316,21 @@ Gets the license info of the license used to activate the LexFloatServer
   "organization": null
 }
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 ## Getting the list of floating licenses
 
 LexFloatServer exposes a floating-licenses API endpoint that can be used to get the leased floating licenses.
 
-{% swagger baseUrl="http://localhost:8090" path="/api/floating-licenses" method="get" summary="Gets the list of floating licenses" %}
-{% swagger-description %}
+## Gets the list of floating licenses
+
+<mark style="color:blue;">`GET`</mark> `http://localhost:8090/api/floating-licenses`
+
 Gets the current server stats
-{% endswagger-description %}
 
-{% swagger-response status="200" description="" %}
+{% tabs %}
+{% tab title="200 " %}
 ```javascript
 [
   {
@@ -349,19 +352,21 @@ Gets the current server stats
   }
 ]
 ```
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}
 
 ## Getting server license meter attributes
 
 LexFloatServer exposes a license meter attributes API endpoint that can be used to get the list of all the meter attributes of the license used to activate the LexFloatServer.
 
-{% swagger method="get" path="/api/server/license-meter-attributes" baseUrl="http://localhost:8090" summary="Gets the list of license meter attributes" %}
-{% swagger-description %}
+## Gets the list of license meter attributes
+
+<mark style="color:blue;">`GET`</mark> `http://localhost:8090/api/server/license-meter-attributes`
+
 Gets the list of meter attributes of the license used to activate the LexFloatServer
-{% endswagger-description %}
 
-{% swagger-response status="200: OK" description="" %}
+{% tabs %}
+{% tab title="200: OK " %}
 <pre class="language-javascript"><code class="lang-javascript">[
   {
     "id": "string",
@@ -372,5 +377,5 @@ Gets the list of meter attributes of the license used to activate the LexFloatSe
   }
 ]
 </code></pre>
-{% endswagger-response %}
-{% endswagger %}
+{% endtab %}
+{% endtabs %}