Log inSign upBook a demo
Tines Stories
  1. Docs
  2. Admin
  1. Docs
  2. Admin

Custom domains

Last updated

Tines Stories allows customers to either rename their entire tenant to a new domain, or add a custom domain specifically for webhooks and pages. A self-hosted tenant has one hostname, and the UI, API, webhooks, and pages all use it.

Tines Stories Cloud

Tenant renaming

Renaming a tenant allows you to use the new name through the UI, webhooks, pages, API, etc. An example of a tenant rename would be changing it from its autogenerated name (e.g., https://rough-water-2650.tines.com) to domain that is more meaningful to your business (e.g., https://acme.tines.com).

Tenant rename with single sign-on

When renaming a tenant with single sign-on configured, you must follow these steps:

  1. Disable single sign-on.

  2. Change webhook and pages usages

    • It is possible to continue to use the old domain for webhooks and pages, as long as you request that it is added as a custom domain.

  3. Coordinate with your customer success manager (CSM) or Tines Stories Support and confirm your tenant was renamed.

  4. Sign in to your renamed tenant and re-enable single sign-on using the new domain.

Custom domain

Custom domains only apply to webhooks and pages. They will not affect anything else, like the UI. Sharing webhook and page links on a familiar domain can help build trust with your recipients.

If you have a custom domain, you can access pages and webhooks using both the custom domain and the tenant domain.

Find more information on custom domains for pages here.

Tines Workbench Slack App

If you have the Tines Workbench Slack app installed and your tenant is renamed, you will need to reinstall the Slack app. The Workbench Slack app routes messages based on your tenant domain, and a rename will cause it to stop responding until the app is reinstalled.


Self-Hosted

Set the hostname with the DOMAIN environment variable. Point DNS at the deployment and terminate TLS in front of Tines. See SSL/TLS termination in the self-hosted docs.

To change the hostname, update DOMAIN and restart. Tines applies the new domain on startup. Update DNS and the TLS certificate to match. Webhook and page URLs use the new hostname, so update any system that calls the old one.

Single sign-on uses this hostname. After the change, update your identity provider:

  • SAML assertion consumer service: https://<domain>/users/saml/auth

  • SAML metadata: https://<domain>/users/saml/metadata

  • OpenID Connect redirect: https://<domain>/users/oidc

Was this helpful?