Tenant Override System
You can override the configurations for a specific tenant within an application.
Any tenant can be modified differently from the default configuration settings of the application to meet their own requirements. The customization of one tenant does not affect any other tenant in the application. In this way, overriding the configurations for a specific tenant allows for greater customization and flexibility within a multi-tenant application, enabling each tenant to tailor the application to their specific requirements.
Ownership and Overrides
In order to support isolated tenant configurations, Wristband has a system of ownership and overrides. Let's take the identity provider configurations for an application as an example. The application owns a set of identity provider configurations that determine how users log in to the application. By default, when application users land on the login page, they will see the identity provider and login options assigned from the application level.
Tenants also own their own set of identity provider configurations. By default, the identity provider values match that of the application configurations. Each tenant can alter those values of the identity providers solely for themselves. However, changing the values is not enough for users under that tenant to see the new login options on the login page. The tenant override flag must also be enabled. Enabling the override tells Wristband to use the tenant configurations instead of the application configurations. That override flag can be turned on or off at any time.
All App-level Configurations Model
For the case where no tenant within an application has been customized, all tenants inherit their configurations from the application level.
Mixed Configurations Model
In the case where some tenants have overrides enabled, those who do not have overrides enabled will inherit their configurations from the application level.
All Tenant-level Configurations Model
It is also possible to override configurations for every single tenant such that the default application level configurations are never utilized.
Updated 21 days ago