10.10.0.cl docs

modules/ROOT/pages/abac-user-parameters.adoc

@@ -16,7 +16,7 @@ The ABAC feature is disabled by default on ThoughtSpot instances. To enable this
 ====
 
 
-// * The `user_parameters` property in `auth/token/full` and `auth/token/object` APIs used for the beta implementation of ABAC is deprecated in 10.4.0.cl. 
+// * The `user_parameters` property in `auth/token/full` and `auth/token/object` APIs used for the beta implementation of ABAC is deprecated in 10.4.0.cl.
 // * Starting with 10.4.0.cl, security attributes for ABAC will not be stored in the `user` > `user_parameters` object. All ABAC-related security rules and filters applied via token generated using the `/api/rest/2.0/auth/token/custom` API endpoint are stored in the `user` > `access_control_properties` object.
 // * The  +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fauthentication%2Fget-custom-access-token">Custom access token </a>+++ REST API endpoint.
 
@@ -183,7 +183,8 @@ a|All persisted rules and attributes of the user object are replaced with the se
 
 [NOTE]
 ====
-* By default, the `RESET` option resets all attributes. In 10.6.0.cl and later versions, you can specify the attributes  to reset in the `reset_option` attribute. The `reset_option` allows resetting only filter rules, Parameters, or group properties in the token API request.
+* By default, the `RESET` option resets all attributes.
+//* In 10.6.0.cl and later versions, you can specify the attributes  to reset in the `reset_option` attribute. The `reset_option` allows resetting only filter rules, Parameters, or group properties in the token API request.
 * In 10.4.0.cl, the `REPLACE` behavior can be achieved by making a `RESET` request followed by an `APPEND` request, then passing only the `APPEND` request token to the browser.
 ====
 |=====
@@ -223,9 +224,9 @@ To fully remove all persisted `filter_rules` or `parameter_values` from a user o
 The requested token can still be used for ABAC if you included `filter_rules` or `parameter_values` in the request.
 
 === Token request test page
-A downloadable, customizable web page for testing all of the ABAC and trusted authentication capabilities is link:https://github.com/thoughtspot/ts_everywhere_resources/tree/master/examples/abac_with_token_auth[available on GitHub^]. 
+A downloadable, customizable web page for testing all of the ABAC and trusted authentication capabilities is link:https://github.com/thoughtspot/ts_everywhere_resources/tree/master/examples/abac_with_token_auth[available on GitHub^].
 
-The username specified in the test page must have Administrator privilege or you can supply the *secret_key* for the ThoughtSpot instance to request a token for any user along with setting their ABAC properties. 
+The username specified in the test page must have Administrator privilege or you can supply the *secret_key* for the ThoughtSpot instance to request a token for any user along with setting their ABAC properties.
 
 See the xref:trusted-authentication.adoc[trusted authentication] documentation for full details on proper setup to allow trusted authentication.
 
@@ -237,7 +238,7 @@ Starting in ThoughtSpot 10.4.0.cl, you can add `is_mandatory_token_filter: true`
 
 ThoughtSpot checks to see if the logged-in user has any `filter_rules` defined for a column marked with `is_mandatory_filter: true`, and denies access to any data if a filter rule for the matching column is not found.
 
-=== Show All 
+=== Show All
 The way to show all values for a column protected by `is_mandatory_token_filter: true` is to pass the special keyword `["TS_WILDCARD_ALL"]` as the value for the column in the `filter_rules`.
 
 Columns without `is_mandatory_token_filter: true` will show all values if there is no `filter_rule` for that column.
@@ -260,7 +261,7 @@ You can retrieve the attribute names and values from any source: the embedding a
 
 ==== Translate entitlements into filter rules
 
-Filter rules *match on the name property of a column* as defined in ThoughtSpot, not the column's name in the underlying database table. 
+Filter rules *match on the name property of a column* as defined in ThoughtSpot, not the column's name in the underlying database table.
 
 The xref:trusted-auth-token-request-service.adoc[token request service] *MUST* know the ThoughtSpot column names that will be used for each of the attributes, so you'll need to coordinate between ThoughtSpot Worksheet designers and the xref:trusted-auth-token-request-service.adoc[token request service] to make sure the matching column names and values are being sent.
 
@@ -308,7 +309,7 @@ The following is a request where a different user can see all `Region`, but stil
 [source,javascript]
 ----
 "filter_rules": [
-   { 
+   {
      "column_name" : "Customer ID",
      "operator": "EQ",
      "values": ["TS_WILDCARD_ALL"]
@@ -399,7 +400,7 @@ The basic form of the SQL Pass-through function is:
 
 `sql_passthrough_function("<sql_statement>", <ThoughtSpot variable 1>, <ThoughtSpot variable 2>,...)`
 
-The proper pass-through function to use in most cases is `sql_bool_op`, which can be used in a filter set to `true` as xref:#worksheet-filter[shown above]. 
+The proper pass-through function to use in most cases is `sql_bool_op`, which can be used in a filter set to `true` as xref:#worksheet-filter[shown above].
 
 The list of variables after are substituted into the SQL statement using curly braces in the order listed, starting at 0:
 
@@ -460,7 +461,7 @@ For indexing recommendations, see xref:abac-user-parameters.adoc#_configuration_
 
 ////
 * Several features within ThoughtSpot, such as autocompletion in Search on values within columns or the suggestions in *Explore* mode, use ThoughtSpot indexing. Due to the runtime nature of ABAC via tokens, ThoughtSpot indexing will not be restricted by the values supplied in a token.
-+ 
++
 You must turn off indexing for any field that needs to be restricted by RLS when using ABAC via tokens for RLS, or also include an RLS Rule on fields that must also be filtered for the Indexing system.
 
 

modules/ROOT/pages/api-changelog.adoc

@@ -8,6 +8,30 @@
 
 This changelog lists only the changes introduced in the Visual Embed SDK. For information about new features and enhancements available for embedded analytics, see xref:whats-new.adoc[What's New].
 
+== Version 1.39.0, July 2025
+
+[width="100%" cols="1,4"]
+|====
+|[tag greenBackground]#NEW FEATURE#  a| *Spotter embed components with new names* +
+The following Spotter embed components are now deprecated and replaced with new components in the SDK and Visual Embed Playground:
+
+* `ConversationEmbed` +
+Replaced with `SpotterEmbed`
+* `ConversationViewConfig` +
+Replaced with `SpotterEmbedViewConfig`
+* `BodylessConversation` +
+Replaced with `SpotterAgentEmbed`
+* `BodylessConversationViewConfig` +
+Replaced with `SpotterAgentEmbedViewConfig`
+
+The deprecated components with old names in the existing Spotter embed implementations will continue to function until further notice. For code samples with new component names, see xref:embed-spotter.adoc[Spotter embed documentation].
+|[tag greenBackground]#NEW FEATURE# a| *Action ID of Spotter coaching* +
+For ThoughtSpot instances that have the new Spotter feedback and coaching workflow enabled, SDK provides the action ID `Acion.InCoversationTraining` to manage the visibility of the *Add to coaching* button on Answer generated from Spotter prompts.
+
+[NOTE]
+The new Spotter feedback and coaching workflow is a beta feature and is turned off by default.
+|====
+
 == Version 1.38.0, June 2025
 
 [width="100%" cols="1,4"]
@@ -37,21 +61,6 @@ In full app embedding, you can now hide the following columns on the *Liveboards
 `hiddenListColumns: [ListPageColumns.Share]` +
 
 For more information, see xref:full-app-customize.adoc#_hide_columns_on_list_pages_new_experience[Customize full application embed].
-
-|[tag greenBackground]#NEW FEATURE#  a| *Spotter embed components with new names* +
-The following Spotter embed components are now deprecated and replaced with new components:
-
-* `ConversationEmbed` +
-Replaced with `SpotterEmbed`
-* `ConversationViewConfig` +
-Replaced with `SpotterEmbedViewConfig`
-* `BodylessConversation` +
-Replaced with `SpotterAgentEmbed`
-* `BodylessConversationViewConfig` +
-Replaced with `SpotterAgentEmbedViewConfig`
-
-The deprecated components with old names in the existing Spotter embed implementations will continue to function until further notice.
-For more information, see xref:whats-new.adoc#_spotter_embed_components[What's new] and xref:embed-spotter.adoc[Spotter embed documentation].
 |====
 
 == Version 1.37.0, April 2025

modules/ROOT/pages/authentication.adoc

@@ -589,18 +589,9 @@ Does not update the existing user properties. The attributes defined in the API
 Available from 10.5.0.cl. Replaces existing user properties of the user with the new attributes assigned to the token in the API request.
 
 * `RESET` +
-Resets the existing user properties upon token generation and adds the new attributes defined in the request. By default, `"persist_option": "RESET"` resets all attributes, unless a specific `reset_option` is defined.
+Resets the existing user properties upon token generation and adds the new attributes defined in the request. By default, `"persist_option": "RESET"` resets all attributes
 
-|`reset_option` a|__Array of strings__. Allows you to define the type of attributes to reset upon token generation. The following options are available:
-
-* `FILTER_RULES` +
-Resets filter attributes.
 
-* `PARAMETERS`
-Resets only Parameters.
-
-* `GROUPS`
-Resets group assignments
 
 |`filter_rules`  a|__Array of filter rules__. An array of runtime filter conditions to pass via token. Each rule in the array must include the following information:
 
@@ -671,6 +662,22 @@ __Optional__|__Boolean__. Available from 10.5.0.cl. Creates a user if the specif
 __Optional__|__Array of Strings__. GUIDs or names of the groups to assign the user to. This attribute can be used in conjunction with `auto_create` to dynamically assign groups and privileges to a user.
 |=====
 
+
+
+//unless a specific `reset_option` is defined.
+////
+|`reset_option` a|__Array of strings__. Allows you to define the type of attributes to reset upon token generation. The following options are available:
+
+* `FILTER_RULES` +
+Resets filter attributes.
+
+* `PARAMETERS`
+Resets only Parameters.
+
+* `GROUPS`
+Resets group assignments
+////
+
 ==== Example request
 
 [source,cURL]

modules/ROOT/pages/common/nav.adoc

@@ -108,6 +108,7 @@
 *** link:{{navprefix}}/set-locale[Customize locale]
 *** link:{{navprefix}}/custom-domain-config[Custom domain configuration]
 *** link:{{navprefix}}/customize-emails[Customize onboarding settings]
+*** link:{{navprefix}}/customize-email-apis[Customize email template]
 *** link:{{navprefix}}/in-app-navigation[Create dynamic menus and navigation]
 ** link:{{navprefix}}/VisualEmbedSdk[Visual Embed SDK Reference]
 include::generated/typedoc/CustomSideNav.adoc[]
@@ -209,13 +210,18 @@ include::generated/typedoc/CustomSideNav.adoc[]
 
 *  link:{{navprefix}}/development-and-deployment[Deployment and integration]
 ** link:{{navprefix}}/development-and-deployment[Development and deployment]
+*** link:{{navprefix}}/thoughtspot-objects[ThoughtSpot objects overview]
 *** link:{{navprefix}}/git-integration[Deploy with Git]
 **** link:{{navprefix}}/git-configuration[Configure Git integration]
 **** link:{{navprefix}}/git-api[Version Control REST APIs]
 **** link:{{navprefix}}/guid-mapping[GUID mapping]
 *** link:{{navprefix}}/deploy-with-tml-apis[Deploy with TML APIs]
-*** link:{{navprefix}}/thoughtspot-objects[ThoughtSpot objects]
-*** link:{{navprefix}}/modify-tml[TML modification]
+**** link:{{navprefix}}/modify-tml[TML modification]
+*** link:{{navprefix}}/publish-data-overview[Publish content to Orgs ^Beta^]
+**** link:{{navprefix}}/variables[Define variables ^Beta^]
+**** link:{{navprefix}}/parameterze-metdata[Parameterize metadata ^Beta^]
+**** link:{{navprefix}}/publish-to-orgs[Publish objects to Orgs ^Beta^]
+
 ** link:{{navprefix}}/multi-tenancy[Multi-tenancy]
 *** link:{{navprefix}}/orgs[Multi-tenancy with Orgs]
 *** link:{{navprefix}}/multitenancy-within-an-org[Multi-tenancy within an Org]

modules/ROOT/pages/customize-email-apis.adoc

@@ -0,0 +1,129 @@
+= Customize email template [beta betaBackground]^Beta^
+
+:page-title: Customize notification email settings per Org
+:page-pageid: customize-email-apis
+:page-description: You can rebrand system-generated notifications and customize notification emails
+
+
+
+ThoughtSpot now provides REST APIs that enable developers and administrators to customize the branding, content, and visibility of components in notification emails.  ThoughtSpot embedded users receive notification emails for several events, including:
+
+* ThoughtSpot welcome emails
+* Sharing of Liveboards, visualizations, or saved answers
+* SpotIQ analysis results
+* KPI chart alerts
+
+These APIs support customizations of the following parameters of the email template at the Org level:
+
+* Style customization, including font and email colour palette, allows you to set the look and feel, including fonts and colours, for a seamless product experience.
+* Custom vocabulary for notification emails. This allows you to replace ThoughtSpot specific terms like “ThoughtSpot,” “Liveboard,” “Answer,” and "SpotIQ," with your product terminology.
+* Customizing the company logo and the company contact details in the email footer.
+* Customizing the visibility of actions like unsubscribe and mobile app nudge.
+* Customizing the visibility of the *Privacy Policy* and *Manage Notification Preferences* components.
+
+[NOTE]
+====
+These APIs are in beta and disabled by default on ThoughtSpot instances. To enable these APIs on your instance, contact ThoughtSpot support.
+====
+
+== Before you begin
+
+* For REST API v2 operations, the Org context is determined based on the authentication token used in your API requests. Ensure you log in to the appropriate Org context from which you want to send API requests.
+* Ensure that you have developer or administrator privileges for the Org.
+
+[NOTE]
+====
+For overlapping components, customized configuration through these APIs overrides the email configuration through the *Admin* > *Onboarding* page of your ThoughtSpot instance.
+====
+
+
+
+//To try the API endpoints for the email customizations, see xref:rest-api-v2-reference.adoc[REST APIs v2].
+
+== Create an email customization
+To customize the notification emails for your Org, send a `POST` request to the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Femail-customisation%2Fcreate-email-customisation"> /api/rest/2.0/customization/email </a>+++ API endpoint, with the following parameters in the request body.
+
+At any given time, only one customized configuration can be set for the notification emails of the Org. The most recently set configuration will be the active one.
+[NOTE]
+====
+The customized configuration set for the Org overrides the configuration set for the ThoughtSpot instance. However, any Org with no specific configuration will reflect the same configuration as for the ThoughtSpot instance.
+====
+
+
+
+=== Request parameters
+In your `POST` request body, include the following parameters:
+
+[width="100%" cols="1,4"]
+[options='header']
+|=====
+|Parameter|Description
+
+|template_properties a|__String__. Required. A JSON map of customizable elements of the email.
+|=====
+
+==== Example request
+[source,CURL]
+----
+curl -X POST \
+  --url 'https://{ThoughtSpot-Host}/api/rest/2.0/customization/email'  \
+  -H 'Accept: application/json' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer {AUTH_TOKEN}' \
+  --data-raw '{
+  "template_properties": {
+    "ctaButtonBgColor": "",
+    "ctaTextFontColor": "",
+    "primaryBgColor": "",
+    "hideMobileAppNudge": false,
+    "fontFamily" : "",
+    "hideProductName" : false,
+    "hideFooterPhone" : false,
+    "hideFooterAddress" : false,
+    "hidePrivacyPolicy" : false,
+    "hideManageNotification" : false,
+    "hideTsVocabularyDefinitions": false,
+    "hideNotificationStatus" : false,
+    "textTransform": "",
+    "replacementValueForLiveboard": "LB dashboard",
+    "replacementValueForAnswer": "Answer dashboard",
+    "replacementValueForSpotIQ": "SpotIQ dashboard",
+    "hideErrorMessage": false,
+    "hideUnsubscribeLink" : false,
+    "hideModifyAlert": false,
+    "productName":"ThoughtSpot",
+    "footerPhone":"(800) 508-7008",
+    "footerAddress":"444 Castro St, Suite 1000 Mountain View, CA 94041"
+  }
+}'
+----
+
+
+[.widthAuto]
+[.bordered]
+image:./images/email-template.png[JSON actions explained]
+
+
+== Validate the email customization
+To validate your email customization configuration in ThoughtSpot, send a `POST` request to the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Femail-customisation%2Fdelete-email-customisation">  /api/rest/2.0/customization/email/validate </a>+++ API endpoint.
+This triggers a test email that reflects all the customizations you have configured. It allows you to confirm that customizations are applied as expected. You can adjust your configuration if needed and repeat the validation until done.
+
+For users with developer privileges, the email will be sent to their email id. For users with admin privileges, the email will be delivered to the address associated with the ThoughtSpot account.
+
+[NOTE]
+====
+Validation email delivery requires the mail service to be enabled for the Org. If email configuration is missing, emails will not be sent or received, regardless of the API response.
+====
+
+
+== Search an email customization
+To search the email customization configuration set for the Org send a  `POST` request to the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Femail-customisation%2Fsearch-email-customisation"> /api/rest/2.0/customization/email/search </a>+++ API endpoint.
+
+
+== Delete an email customization
+To remove an existing customization configuration for notification emails in your Org, send a `POST` request to the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Femail-customisation%2Fdelete-email-customisation"> /api/rest/2.0/customization/email/{template_identifier}/delete </a>+++ API endpoint, with the `template_identifier` passed as a path parameter in the request URL .
+
+== Additional references
+
+* xref:customize-email-settings.adoc[Customize onboarding settings]
+* xref:custom-domain-configuration.adoc[Custom domain configuration]

modules/ROOT/pages/customize-email-settings.adoc

@@ -68,4 +68,4 @@ Enter the URL that you want to use as a sign-up button link.
 
 + 
 . Click *Save changes*.
-. To reset the email and onboarding settings to the application default, click *Reset configuration*.
+. To reset the email and onboarding settings to the application default, click *Reset configuration*.