Tenant Override System
Wristband uses an override system to let you customize the login process for each tenant.
Wristband utilizes a two-level hierarchical configuration model:
- Application level (Top): Defines the default global configurations.
- Tenant level (Bottom): Inherits parent settings but supports overrides for a customized authentication experience.
Identity Provider Tenant Override Example
To illustrate Wristband's hierarchical configuration, here are examples of how Identity Provider (IdP) settings are managed across an application's tenants.
Application Configuration Inheritance
To start, only the Wristband IdP is enabled at the application level.
Figure 1: Tenants inherit the application-level Wristband identity provider configuration when no tenant override is enabled.
As shown in Figure 1, neither Tenant A nor Tenant B uses overrides. They both inherit the application-level configuration, meaning users from both tenants can only log in via the Wristband identity provider.
Tenant-Level Overrides
To allow Tenant B users to authenticate via Google Workspace, configure Google Workspace as an identity provider specific to Tenant B. Once configured, activate the identity provider override toggle for Tenant B to bypass the application default.
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 results in two distinct login experiences:
Tenant B: Displays the Google Workspace login option instead of the native Wristband identity.
Tenant A: Continues to inherit the application-level settings and displays only the default Wristband login.
Remember to Enable Tenant Override TogglesTenant configurations do not apply automatically upon creation or modification. To make a tenant-level configuration active, you must enable its corresponding override toggle.
Updated 4 days ago