Multi-client applications enable you to build and maintain an application once, and make it available to multiple clients. Each client will have a separate environment with separate users and data, and the application can be themed differently. This is particularly helpful for law firm customers to onward-sell applications to their clients.
If you are an author, learn how to make an application available to clients.
This is a licensed feature; pricing to be discussed with your BRYTER contact person. If you would like to trial this feature, please get in touch with them or via support@bryter.io.
Multi-client applications overview
To enable your authors to make an application available to multiple clients, first create an additional Live environment for each client. Then, configure it:
- Select a custom theme to ensure the applications displayed to end users will be branded specifically to your client.
- Manage end user accounts: Configure how the client's end users authenticate and log in to access their applications. You can manually add end users with username and password, and you can add identity providers. This will enable end users to automatically sign up with their Microsoft account, their Okta account, or similar. You can also create client-specific user groups that authors can later use for managing end user access to an application.
- With every environment, a portal is created that displays an applications' overview a client's end users can access. You can configure who can access what.
- Configure a data retention policy: Schedule if and when data on end user sessions and from databases should be deleted.
Once you have created a client environment, authors can make their applications available to the client via a client environment.
Benefits of this feature over duplicating an application for each client
- Faster rollout: Build one → sell to many! Publish your applications to numerous additional live environments, on top of the built-in LIVE environment
- Centralized maintenance, reduced efforts: Push updates to all clients at once. When you make changes to an application made available to clients and publish those changes to Live, all clients will get that change automatically.
- Secure separation of client data: Each client can only ever access their own data.
- Separate user and authentication management: Each client has a separate user and group base. Users can be provisioned via Username and password or through different identity providers, allowing each client to manage their own users via SSO
- Access permissions: Each client’s users can only ever access content published in their client environment. Access permissions can be additionally restricted, making applications or individual modules and data views accessible to specific end users or groups only
- Consistent theming per client, white-labeled or according to company’s design, within the client portal and across multiple applications