Tenant Override System
Wristband uses an override system to let you customize each tenant.
Hierarchical Configuration Model
Wristband uses a two-level hierarchical configuration model to manage settings across applications and their tenants:
- Application level: Defines the default configurations inherited by all tenants within the application.
- Tenant level: Inherits application-level settings by default but supports overrides to customize the authentication experience for individual tenants.
Identity Provider Tenant Override Example
The following example demonstrates how Identity Provider (IdP) configurations are inherited from the application level and overridden at the tenant level.
Application-Level Configuration
Initially, only the Wristband IdP is enabled at the application level. All tenants inherit this configuration unless they override it.

Figure 1: Tenants inherit the application-level Wristband identity provider configuration when no tenant override is enabled.
Tenant-Level Overrides
To allow users in Tenant B to authenticate with Google Workspace, configure Google Workspace as an identity provider for Tenant B. Then, enable the tenant's identity provider override to bypass the application-level configuration and use Tenant B's identity provider settings instead.

Figure 2: Tenant B overrides the application-level configuration to use Google Workspace, while Tenant A continues to inherit the default Wristband identity provider.
This configuration creates two distinct login experiences:
- Tenant B: Displays the Google Workspace login option instead of the default Wristband login.
- Tenant A: Continues to inherit the application-level configuration and displays only the default Wristband login.
Enable Tenant Override TogglesTenant-level configuration changes do not take effect until the corresponding override toggle is enabled. Be sure to enable the appropriate toggle for each tenant configuration you want to apply.
Updated 7 days ago