Tenants
A tenant is a grouping of users who have access to a common set of data, configurations, and security settings.
Each tenant has its own unique set of data, configurations, and security settings, which are isolated from other tenants, but they share the underlying infrastructure and resources, such as the database and server. In Wristband, multiple tenants can live under a single application, and multiple users can live under a single tenant.
Every tenant can be customized to meet their specific needs and can conceptually represent any of the following for your application:
- Organizations
- Companies
- Teams
- Accounts
- Workspaces
Types of Tenants
In Wristband, there are three different types of tenants: STANDARD
, GLOBAL
, and STANDALONE
. The tenant type can be chosen at the time of tenant creation, and that type is immutable.
Standard Tenants
Standard tenants are used to represent organizations within a multi-tenant application. Each standard tenant has its own login page that is fully customizable. Users belonging to standard tenants must log in to your application using their tenant-specific login page. Users are able to discover which standard tenants they belong to by going through the tenant discovery flow.
Standard tenants will see both application-specific and tenant-specific language on the Wristband-hosted Tenant Login Pages and in the transactional email templates.
Global Tenant
Global tenants are meant to store consumer users that are not associated with an organization. Only one global tenant can be created per application.
Global Tenant Differences
Global tenants are excluded from tenant discovery results when a user enters an email address on the Tenant Discovery Page that is associated with multiple tenants. They also cannot have Enterprise External Identity Providers because a 1-to-1 scoping to an organization is not possible.
All users of a global tenant share the same Tenant Login Page. For global tenants, any hosted pages and transactional emails will offer a consumer-like login experience by removing tenant-specific language from the UI. Typically, users will navigate directly to the Global Tenant Login Page URL when accessing your application.
You can also enable the Login Workflow Policy to display a "Log In with Your Organization" link on the Global Tenant Login Page which will send users to the Tenant Discovery Page. This provides a seamless hybrid experience for both consumer and organization-specific needs throughout your application.
Stand-alone Tenants
Stand-alone tenants can be used to provide a completely white-labeled experience. There's no restriction on the number of stand-alone tenants that can be created for an application.
For stand-alone tenants, any language regarding the application is removed from all hosted pages and transactional emails. Only the tenant-specific information will be displayed. Likewise, any links that allow for changing to a different Tenant Login Page will be removed.
Updated 24 days ago