Customize links
# dev-help
s
Hi. We are trying to enable schedules to our customers. We are using AppEmbed and have more than 1000 orgs. When end user gets scheduled liveboard, it contains a link in two places - logo and CallToAction button. We tried email customization but could not see any option to disable / customize those links. Is there a way to remove this link in scheduled email? Our application's URL follows the following naming pattern https://./ eg https://client1.example.com.au/insights or https://client2.example.co.nz/insights and URL for thoughtspot cluster is https://companyName1.thoughtspot.cloud and we mave multiple clusters. In one of docs https://developers.thoughtspot.com/docs/customize-links#_verify_system_generated_links, I found out that there is "per Org custom embed URL feature" but not sure if it helps or not. I have attached a screenshots for email notification for liveboard sharing and scheduled email. Also, is there way to disable all emails except scheduled emails? Thank you. https://cdn.discordapp.com/attachments/1143209464875462756/1494174457470910464/Screenshot_2026-04-16_at_1.08.23_PM.png?ex=69e1a5e7&is=69e05467&hm=a04166b07af9274fe7785846729a6681d415d3b7a2942b7f2bfaddb0714208f5& https://cdn.discordapp.com/attachments/1143209464875462756/1494174458171101286/Screenshot_2026-04-16_at_1.10.41_PM.png?ex=69e1a5e7&is=69e05467&hm=8e11cb54d09843d5fc637faf2a236db24d7f4ed9d160dc831b9aadb4bf989f6d&
s
Hi @Suresh - ELMO : Could you please raise a support request
s
Great questions — and yes, the per-Org custom embed URL is relevant for your setup. ### 1) Can you remove the link from scheduled Liveboard emails (logo + CTA)? From the official docs/APIs, I could not find a setting to completely remove the object navigation link in scheduled/share emails. What is supported: - You can customize where links point (via custom link settings, and optionally per-Org behavior). - In scheduling UI, when custom URL is configured, users can use “Use custom URL in email link” so scheduled email links use your custom format. - In email template customization, you can change things like
home_url
,
company_website_url
, logo URL, colors, text labels, and hide certain footer/auxiliary elements — but no documented field to remove the core CTA/object link entirely. So for your multi-tenant pattern (
https://<tenant>.<domain>/<product>
), the right path is usually: - configure custom links + verify generated links, - and use per-Org custom embed URL behavior if enabled, so emails route recipients to your tenant-facing app URL instead of raw cluster URL. ### 2) Does per-Org custom embed URL help? Yes, likely. Docs indicate that with per-Org custom embed URL enabled, generated embedded links can include Org context, and scheduled email flow supports using custom URL format. This is exactly the feature family to align links with your tenant routing model. ### 3) Can you disable all emails except scheduled emails? I could not find a single global “only scheduled emails” switch in the official docs returned. What I did find: - Email customization APIs let you customize template fields/visibility (branding/content components). - These APIs are about template presentation and certain elements, not a documented global notification-type suppression matrix.
- Unsubscribe/manage-notification links and user notification preferences are part of the model, but that is not equivalent to an admin-level “disable all except scheduled” control in the material I found. --- ### Recommended next steps for your case 1. Enable/validate custom link configuration and verify scheduled emails use custom URL format. 2. Use per-Org custom embed URL (if available on your instance) to preserve tenant/org context. 3. Use email customization APIs (
searchEmailCustomization
,
updateEmailCustomization
) for branding and optional visibility tweaks, but don’t expect removal of the main CTA link from scheduled emails. 4. For strict suppression policy (“only scheduled emails”), raise with ThoughtSpot Support/CSM — especially since parts of email customization are marked Beta / feature-flagged. If you want, I can draft a concrete rollout checklist for 1000+ orgs (including API-driven org-by-org validation strategy and failure handling across multiple clusters).
s
I have created a support case. Thank you.