There are some situations in which it makes sense to create multiple sub-accounts in your CommandBar account. The most common example of this is to create multiple CommandBar accounts for different “venues” in which you want to deploy CommandBar, like multiple products or a product and a marketing site.
The CommandBar term for a sub-account is a “tenant”.
Using tenants (instead of multiple accounts) has the advantage of applying the same account settings to each sub-account.
How do I create a new tenant?
Tenants are only available to customers on Growth and Enterprise plans. Please reach out to our team via Intercom, Slack, or firstname.lastname@example.org if you want to add a new tenant. Make sure to include the name of the new tenant.
How do I delete a tenant?
To delete a tenant, message the team via Intercom, Slack, or email@example.com with (a) the name of the tenant; (b) the organization ID in your request.
Can a user be a member of one tenant but not another?
This is not possible as of now, but let us know if you are interested in this functionality. We’d love to hear more about your use case as we are actively improving our access control system.
If a user is a member of one tenant, then they can access all connected tenants.
What settings persist across tenants?
Nearly all account settings persist across tenants, including
- Editor seats
- Ability to use custom CSS
- Integration access
What settings don’t persist across tenants?
Implementation details (i.e. your CommandBar configuration) do not persist across tenants. This includes
- Building blocks (content, pages, actions, etc.)