thoughtspot · roza-leyderman-pro · Jul 11, 2019 · Jul 11, 2019
diff --git a/_app-integrate/data-api/about-data-api.md b/_app-integrate/data-api/about-data-api.md
@@ -1,22 +1,26 @@
 ---
-title: [About the REST API]
+title: [About the Data REST API]
 keywords: REST,API,data,authentication,public
 last_updated: tbd
 summary: "The purpose of the REST API is to get data out of ThoughtSpot so you can use it in a Web page, portal, or application."
 sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
-When using the REST API, authentication is achieved through SAML. After authentication, use the POST method to call a URL for the desired visualization or pinboard. A JSON (JavaScript Object Notation) representation of the data will be returned.
+When using the Data REST API, authentication is achieved through SAML. After authentication, use the POST method to call a URL for the desired visualization or pinboard. A JSON (JavaScript Object Notation) representation of the data will be returned.
 
 ## Authentication
 
-Before you can use the REST API, you must authenticate to ThoughtSpot using SAML with the [JavaScript API]({{ site.baseurl }}/app-integrate/JSAPI/about-JS-API.html#).
+Before you can use the Data REST API, you must authenticate to ThoughtSpot using SAML with the [JavaScript API]({{ site.baseurl }}/app-integrate/JSAPI/about-JS-API.html#).
 
 ## Cross Domain Verification
 
-You'll need to enable cross domain verification when using the REST API. This protects your data, so that another website cannot use a URL to get data from ThoughtSpot. The procedure for [enabling the JavaScript API]({{ site.baseurl }}/app-integrate/JSAPI/enable-JS-API.html#) includes information on how to enable this.
+You'll need to enable cross domain verification when using the Data REST API. This protects your data, so that another website cannot use a URL to get data from ThoughtSpot. The procedure for [enabling the JavaScript API]({{ site.baseurl }}/app-integrate/JSAPI/enable-JS-API.html#) includes information on how to enable this.
 
+<<<<<<< HEAD
 ## REST API Capabilities
+=======
+## Data REST API capabilities
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
 
 Use a POST method to access the URL, which calls the REST API. The data is returned as a JSON string. When using this method, you'll need to extract the data from the JSON file and render it on your Web page, portal, or application.
 

diff --git a/_app-integrate/data-api/calling-rest-api.md b/_app-integrate/data-api/calling-rest-api.md
@@ -1,11 +1,11 @@
 ---
-title: [Calling the REST API]
+title: [Calling the Data REST API]
 keywords: API,URL,calling,REST,"REST API"
 last_updated: tbd
 sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
-To call the REST API, you'll specify a URL using the POST method, passing the ID numbers of the objects from which you want to obtain data.
+To call the Data REST API, you'll specify a URL using the POST method, passing the ID numbers of the objects from which you want to obtain data.
 
 ## Specify the pinboard or visualization example
 

diff --git a/_app-integrate/data-api/response-pagination.md b/_app-integrate/data-api/response-pagination.md
@@ -1,13 +1,13 @@
 ---
-title: [REST API pagination]
+title: [Data REST API pagination]
 keywords: REST,API,pagination,JSON,"REST API"
 last_updated: tbd
 summary: "You can paginate the JSON response that is called from the REST API. The order of the data is retained from page to page."
 toc: false
 sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
-Given the ability to paginate, you can quickly populate tables and make new REST calls every time you go to the next page of the data on the table. There is significant load time if you want to populate the data table with many rows (greater than 1000) from the REST API.
+Given the ability to paginate, you can quickly populate tables and make new REST calls every time you go to the next page of the data on the table. There is significant load time if you want to populate the data table with many rows (greater than 1000) from the Data REST API.
 
 To paginate results in your API response, you'll need to add new parameters to the query:
 

diff --git a/_app-integrate/data-api/use-data-api-read.md b/_app-integrate/data-api/use-data-api-read.md
@@ -1,14 +1,20 @@
 ---
-title: [Use the REST API to get data]
+title: [Use the Data REST API to get data]
 keywords: REST,API,data,"REST API"
 last_updated: tbd
 summary: "This procedure shows how to use the REST API to get data out of ThoughtSpot, so you can use it in a Web page, portal, or application. "
 sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
+<<<<<<< HEAD
 Data is returned as JSON (JavaScript Object Notation). Before you can use the REST API, you need to eEnable the JavaScript API (JS API)]({{ site.baseurl }}/app-integrate/JSAPI/enable-JS-API.html#) and authenticate to ThoughtSpot.
+=======
+Data retrieved using the Data REST API is returned as JSON (JavaScript Object Notation).
 
-Use this procedure to construct the URL you will use to call the REST API:
+Before you can use the Data REST API, you need to enable the [JavaScript API (JS API)]({{ site.baseurl }}/app-integrate/JSAPI/enable-JS-API.html#) and authenticate to ThoughtSpot.
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
+
+Use this procedure to construct the URL you will use to call the Data REST API:
 
 1. Log in to ThoughtSpot from a browser.
 2. Navigate to the pinboard from which you want to get data. If it doesn't exist yet, create it now.
@@ -50,5 +56,10 @@ Use this procedure to construct the URL you will use to call the REST API:
 
 6. If you want to apply any filters to the data that will be returned, apply [Runtime Filters]({{ site.baseurl }}/app-integrate/runtime-filters/about-runtime-filters.html#).
 7. Now your URL is complete, and you can use it to access the data directly via the HTTP POST method.
+<<<<<<< HEAD
   The REST API returns the data formatted as JSON.
+=======
+  The Data REST API returns the data formatted as JSON.
+
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
 8. Retrieve the data from the JSON and display it in your Web page, Web portal, or application.
diff --git a/_app-integrate/introduction/introduction.md b/_app-integrate/introduction/introduction.md
@@ -1,8 +1,68 @@
 ---
-title: [Introduction]
+title: [Introduction to Embedding]
 keywords: tbd
 last_updated: tbd
 sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
+<<<<<<< HEAD
 This guide explains how to integrate ThoughtSpot with other applications, including authentication, embedding, and APIs. For information on how to integrate with other data sources for loading data, refer to the Data Integration Guide.
+=======
+ThoughtSpot Extended Enterprise Edition lets you give people outside of your company access to some ThoughtSpot capabilities within the context of an external application, website, or portal. We’ll call these people “external users”. For example, you could give external users access to data, search, search results, data visualizations, and/or pinboards.
+
+External users cannot be granted administrative privileges or receive technical support from ThoughtSpot. All first line support is to be handled through your company or organization.
+
+ThoughtSpot Extended Enterprise Edition includes these capabilities:
+
+- [Full Application Embedding]({{ site.baseurl }}/app-integrate/embedding-viz/about-full-embed.html)
+
+- [Embedded Charts and Pinboards]({{ site.baseurl }}/app-integrate/embedding-viz/embed-a-viz.html)
+
+- [Data REST API]({{ site.baseurl }}/app-integrate/data-api/about-data-api.html)
+
+- [Runtime Filters]({{ site.baseurl }}/app-integrate/runtime-filters/about-runtime-filters.html)
+
+- [Metadata API]({{ site.baseurl }}/app-integrate/reference/metadata-api.html)
+
+When you buy ThoughtSpot Extended Enterprise, the following rights and obligations apply:
+
+1. External users may only access those elements that are exposed through ThoughtSpot public APIs. These include search, search results and data visualizations, saved pinboard and answers, SearchIQ, and SpotIQ.
+2. External users may not be granted Administrator privileges such as the ability to create and modify users and groups.
+3. External users are not permitting to copy or download the ThoughtSpot software.
+4. You may not include external users in a group that has access to these privileges:
+   - Can administer ThoughtSpot
+   - Can administer and bypass RLS
+5. The license for Extended Enterprise does not enable you to act as an MSP (Managed Service Provider). This means that you must not offer managed services to third parties that are based on the ThoughtSpot software.
+6. As a company offering access to ThoughtSpot Extended Enterprise to external users, you are responsible for your own data policy and for complying with local laws and regulations concerning data privacy, such as GDPR and HIPAA.
+7. If you are using one of these capabilities, a NPS (Net Promoter Score) survey will be offered to your external users. You may not disable this survey:
+   - Application Embedding
+   - Embedded Search
+
+If you’re using one of these types of embedding, it is okay to disable the NPS survey:
+   - Visualization Embedding
+   - Pinboard Embedding
+
+8. Deployments of ThoughtSpot Extended Enterprise must conform to the [logo restrictions listed here](https://brand.thoughtspot.com/d/Vtg4Zg2mqTbE/brand-guidelines).
+
+   These are the branding elements you can change in ThoughtSpot Extended Enterprise:
+
+   - [Logos & Favicon]({{ site.baseurl }}/app-integrate/custom-branding/upload-application-logos.html)
+   - [Color Palettes]({{ site.baseurl }}/app-integrate/custom-branding/select-chart-color-palettes.html)
+   - [Background Color]({{ site.baseurl }}/app-integrate/custom-branding/choose-background-color.html)
+   - [Chart and Table Fonts]({{ site.baseurl }}/app-integrate/custom-branding/set-chart-and-table-visualization-fonts.html)
+   - [Footer Text]({{ site.baseurl }}/app-integrate/custom-branding/change-the-footer-text.html)
+
+9. You may not remove the *Powered by ThoughtSpot* logo that appears at the bottom right of the embedded application when using ThoughtSpot full application embed or embedding a pinboard. It is okay to remove the logo if you are embedding a single visualization.
+
+Here are the top level topics on Embedding with Extended Enterprise:
+
+* [Log in to the Linux shell using SSH]({{ site.baseurl }}/app-integrate/introduction/login-console.html)
+* [Login credentials]({{ site.baseurl }}/app-integrate/introduction/logins.html)
+* [Using the JavaScript API]({{ site.baseurl }}/app-integrate/JSAPI/about-JS-API.html)
+* [SAML]({{ site.baseurl }}/app-integrate/SAML/about-SAML-integrations.html)
+* [Data REST API]({{ site.baseurl }}/app-integrate/data-api/about-data-api.html)
+* [Embed ThoughtSpot]({{ site.baseurl }}/app-integrate/embedding-viz/about-embedding-viz.html)
+* [Runtime Filters]({{ site.baseurl }}/app-integrate/runtime-filters/about-runtime-filters.html)
+* [Style Customization]({{ site.baseurl }}/app-integrate/custom-branding/perform-style-customization.html)
+* [API Reference]({{ site.baseurl }}/app-integrate/reference/public-api-reference.html)
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
diff --git a/_app-integrate/reference/metadata-api.md b/_app-integrate/reference/metadata-api.md
@@ -6,7 +6,11 @@ sidebar: mydoc_sidebar
 permalink: /:collection/:path.html
 ---
 
+<<<<<<< HEAD
 These two APIs work with metadata for objects in the system.
+=======
+The Metadata APIs enable you to fetch metadata details for various objects in the ThoughtSpot system. For example, you may want to see the visualization headers of a particular answer or a pinboard.
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
 
 
 ## GET /tspublic/v1/metadata/listobjectheaders

diff --git a/_data/sidebars/mydoc_sidebar.yml b/_data/sidebars/mydoc_sidebar.yml
@@ -784,6 +784,7 @@ entries:
       - title: Search results contain too many blanks
         url: /admin/troubleshooting/search-too-many-blanks.html
         output: web,admBk
+<<<<<<< HEAD
   - sectiontitle: Data Connect
     output: web,cngBk
     sectionitems:
@@ -857,15 +858,94 @@ entries:
         url: /data-connect/reference/data-connect-connection-credentials.html
         output: web,cngBk
   - sectiontitle: Application Integration
+=======
+  # - sectiontitle: Data Connect
+  #   output: web,cngBk
+  #   sectionitems:
+  #   - title: Introduction to Data Connect
+  #     url: /data-connect/setup/ETL.html
+  #     output: web,cngBk
+  #   - title: Prerequisites and Architecture
+  #     url: /data-connect/setup/before-using-data-connect.html
+  #     output: web,cngBk
+  #   - title: Set up ThoughtSpot Data Connect
+  #     url: /data-connect/setup/settingup-etl.html
+  #     output: web,cngBk
+  #   - levelTwoTitle: Work with Data Sources
+  #     output: web,cngBk
+  #     levelTwoItems:
+  #     - title: Add a new data source
+  #       url: /data-connect/setup/adding-data-source.html
+  #       output: web,cngBk
+  #     - title: About changing the schema (DDL)
+  #       url: /data-connect/setup/about-changing-DDL.html
+  #       output: web,cngBk
+  #     - title: About incremental data loads
+  #       url: /data-connect/setup/about-incremental.html
+  #       output: web,cngBk
+  #     - title: Data sources management
+  #       url: /data-connect/setup/data-sources-management.html
+  #       output: web,cngBk
+  #   - levelTwoTitle: Changing the setup
+  #     output: web,cngBk
+  #     levelTwoItems:
+  #     - title: Overview of best practices
+  #       url: /data-connect/making-changes/about-changing-etl-jobs.html
+  #       output: web,cngBk
+  #     - title: Edit a connection
+  #       url: /data-connect/making-changes/edit-a-connection.html
+  #       output: web,cngBk
+  #     - title: Delete a connection
+  #       url: /data-connect/making-changes/delete-a-connection.html
+  #       output: web,cngBk
+  #     - title: Delete a data source
+  #       url: /data-connect/making-changes/delete-data-source.html
+  #       output: web,cngBk
+  #     - title: Stop a scheduled job from running
+  #       url: /data-connect/making-changes/stop-scheduled-job.html
+  #       output: web,cngBk
+  #     - title: Change sharding for a data source
+  #       url: /data-connect/making-changes/change-sharding.html
+  #       output: web,cngBk
+  #     - title: Change a column data type
+  #       url: /data-connect/making-changes/change-data-type.html
+  #       output: web,cngBk
+  #     - title: Add a column to an existing data source
+  #       url: /data-connect/making-changes/add-a-column.html
+  #       output: web,cngBk
+  #     - title: Remove a column from an existing data source
+  #       url: /data-connect/making-changes/remove-column.html
+  #       output: web,cngBk
+  #     - title: Add/remove columns in a loaded table
+  #       url: /data-connect/making-changes/add-remove-columns-in-a-loaded-table.html
+  #       output: web,cngBk
+  #   - levelTwoTitle: Reference
+  #     output: web,cngBk
+  #     levelTwoItems:
+  #     - title: Login for administration
+  #       url: /data-connect/reference/logins.html
+  #       output: web,cngBk
+  #     - title: Best practices
+  #       url: /data-connect/reference/data-connect-insider-tips.html
+  #       output: web,cngBk
+  #     - title: Connectors reference
+  #       url: /data-connect/reference/data-connect-connection-credentials.html
+  #       output: web,cngBk
+  - sectiontitle: Embedding ThoughtSpot using APIs
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
     output: web,apgBk
     sectionitems:
-    - title: Introduction
+    - title: Introduction to Embedding
       url: /app-integrate/introduction/introduction.html
       output: web,apgBk
     - title: Log in credentials
       url: /app-integrate/introduction/logins.html
       output: web,apgBk
+<<<<<<< HEAD
     - title: Get the JavaScript API
+=======
+    - title: Use the JavaScript API
+>>>>>>> 2a3dbdf3c... Add legal for Ext Enterprise Edition
       url: /app-integrate/JSAPI/about-JS-API.html
       output: web,apgBk
     - levelTwoTitle: SAML