Embed without SDK
- Authentication and security settings for iFrame embedding
- URL for embedding in an iFrame
- Embed a Liveboard in an iFrame
- Embed a visualization in an iFrame
- Embed ThoughtSpot Search page in an iFrame
- Embed full application in an iFrame
- Apply runtime overrides (Optional)
- URL format with the per Org feature
- Feature flags and query parameters to customize the embedded view
- iFrame embedding example
- Other methods of embedding without SDK
The Visual Embed SDK is the most convenient way to embed different types of ThoughtSpot content. However, if your portal or system does not have a way to use the Visual Embed SDK JavaScript library, you can embed ThoughtSpot components using an iFrame element. For example, to embed a Liveboard or visualization into applications such as SharePoint, Google Sites, or WordPress, you may want to use an iFrame element.
Authentication and security settings for iFrame embeddingπ
All embedded ThoughtSpot objects require authentication. If the host application does not allow custom Javascript, you can use one of the following authentication methods:
-
Basic authentication with username and password
-
SSO authentication
When doing a direct embed, SAML is typically the only SSO mechanism that can be implemented. If you cannot use the Visual Embed SDK, this typically means the environment you are embedding ThoughtSpot within has restrictions on using JavaScript, which limits the ability to use the Trusted Authentication method for SSO. Any sign-in method to ThoughtSpot creates a session, stored in the browser cookies, so if your platform has a way to complete the trusted authentication flow at some point, even on a different page from where the direct iFrame embed of a Liveboard is located, it may be a viable SSO authentication mechanism.