Help Center
Go back to application
Help Center
Go back to application
Basics
Getting Started
Using the Editor
Pricing, Security and Billing
User Guides
Branding and Appearance
Analytics and Integrations
Developers
Installation
Advanced Integration
User Identity VerificationSites without AuthenticationCustom routingDynamic CSS Classes or AttributesMulti-Tenant ApplicationsHandling Keyboard Shortcuts in ApplicationsExamples of Backend HMAC Computation
JavaScript API
Server-Side (REST) API
Troubleshooting

Multi-Tenant Applications

Typically, there are two types of multi-tenancy. We support both.

Domain-based multi-tenancy

Domain-based multi-tenancy uses (sub)domains for different tenants/users. The application itself is the same, but it's accessed by different domains or subdomains. For example:

  • customer1.yourapp.com
  • customer2.yourapp.com
  • customer3.yourapp.com

We support this scenario out-of-the-box. Once you deploy our JavaScript code to your application it will run on all subdomains.

Note: When creating a workspace, you must enter an Application URL. This URL is used solely for the purpose of the tours/hints editor. You should enter a URL that you can use for building content.

URL-based multi-tenancy and dynamic URLs

URL-based tenancy means that you distinguish users by a parameter in the URL path. For example:

  • yourapp.com/user123/dashboard
  • yourapp.com/user456/dashboard
  • yourapp.com/user789/dashboard

All onboarding content except tours and hints will work without further configuration.

Tours and hints cards have a URL template field, which says where cards should be displayed. For multi-tenancy, follow the Dynamic URLs article. 

Was this article helpful?

Powered by Product Fruits