On the BRYTER platform, you can make an application available to multiple clients. Each client has their own environment that you can publish to.
Each environment has its own brand-compliant theming, a separate user and authentication management, and a secure separation of client data.
The client’s end users can access all applications available to them in a client-specific portal.
You can also publish a shared package to make all of its case databases available to the client environment.
Publish an application to a client environment
Ensure your application is published to Live and your BRYTER admin has created and configured the client environment. Next, proceed as follows:
- In an application, select Publish in the side navigation.
- Click on the expand icon below the Live status to open the section with all created client environments.
- Select one or more clients to whom you would like to make the published application available.
- Select Apply changes.
- In the modal, select Confirm changes.
- Select Open next to a client’s name to open the published application in a new tab. This link is specific to your client’s environment. They can share this link with their end users.
To adapt your selection, click on Edit and repeat steps 3 to 5.
Note that once you have made your application available in a client environment, all your published data views, modules, and pages will offer a new link to view the data view, module, or page in the respective client environment. To open the link, go to the Build page, then, click on the three dot icon in the respective row of the Modules, data views, and pages list.
You can also have some minor customizations across client environments. Learn here how to implement these customizations using a database.
Unpublish an application from a client environment
To remove a published application from a client environment, deselect the respective client environment in the expanded section. The published application will become unaccessible to the client’s end users, but it can be republished to this client’s environment later.
- In an application, select Publish in the side navigation.
- Click on the expand icon below the Live status to open the section with all created client environments, grouped by their publishing status.
- Select Edit.
- Deselect the client environment from which you would like to unpublish the application.
- Select Apply changes.
- In the modal, select Confirm changes. The link to the published application will no longer work for end users of this client and access to the application or any of its modules, data views, or pages will be revoked.
To adapt your selection, select Edit and repeat steps 4 to 6.
Any data stored for the application and its components stays untouched once you have unpublished the application. You can regain access to the data by publishing the application again.If you also want to delete the stored data, ask your BRYTER admin to set up a data retention policy for the client environment.
Known limitations
- Modules, data views, and pages are (un-)published together with the application containing them. You cannot (un-)publish modules, data views, or pages individually to clients.
- Modules and data views are available to all clients in the same version. You cannot roll out a new version to some clients only (however, here is a way to implement minor customizations to a module and its logic).
- While it is not necessary to additionally protect a module with a password, as you can configure end user access, if you decide to password-protect a module, the password of the Live environment will apply to all client environments. You cannot set a client-specific module password.
- Integrations in modules are not environment-specific. The same integration configuration is used on all environments.