What is Multi-client Publishing?
Multi-client Publishing enables you to transition from building Applications with BRYTER for internal use only to selling Applications to your clients.
With Multi-client Publishing, authors build and maintain an Application once and can then make it available to several clients, each with separate users and data, as well as individual themes.
Why would you use Multi-client Publishing?
Multi-client Publishing follows the approach of "Build once, sell many!". Experts can publish entire, consistently-themed, Applications to their target audience and bring together different Modules and Data Views. Updates can be pushed to all clients at once, reducing maintenance efforts significantly.
While BRYTER allows for duplicating of Applications, there are significant benefits to using Multi-client Publishing over duplication Applications in this specific use case:
- Faster rollout
- Reduced maintenance effort
- Consistent theming for each client, white-labeled or according to the company's design
How to use Multi-client Publishing
To publish your Application to multiple clients, you first need to create a client environment and publish the Application from Test to Live.
Follow the links below to be directed to the respective section or review them in order by scrolling down to the next heading.
- How to create client environments
- How to publish applications
- How to make applications available to clients
- How to make applications unavailable to clients
- How to unpublish applications from Test and Live
- How to disable multi-client publishing on my tenant
Create client environments
To get started, access the Admin Console to create and configure client environments. You can think of them as additional LIVE environments. Create one environment for each client by selecting Environments in the navigation sidebar of the Admin Console, then select the blue + New Environment button.
Provide a display name to create the client environment.
The created client environments (currently limited to 10) appear in an overview and are sorted alphabetically. Deactivated environments (if displayed) appear at the bottom.
|[ 1 ] Access Environments
||[ 2 ] Create client environment
||[ 3 ] Show or hide deactivated environments
||[ 4 ] List of available client environments
|[ 5 ] Link to client environment
||[ 6 ] Type indicating whether client environment live or deactivated
||[ 7 ] Configure client environment
||[ 8 ] Exit Admin Console|
Select Configure to set up a client environment. There, the admin can rename the environment, choose a custom theme or deactivate the environment altogether.
|[ 1 ] Return to main environments page
||[ 2 ] Rename client environment
||[ 3 ] Select a custom theme
|[ 4 ] Deactivate client environment
||[ 5 ] Exit Admin Console|
Publish an Application for testing purposes
To publish an Application for testing purposes, publish all Modules that you would like to be part of the Application to TEST in the Module editor first, then publish the Application itself to TEST.
Open the published Application for testing purposes
Selecting the link will open the published Application in a new tab.
Publish an Application to your target audience
To publish an Application to your target audience, publish all Modules that you would like to be part of the Application to LIVE in the Module editor first, then publish the Application itself to LIVE.
Open the published Application for your target audience
Selecting the link will open the published Application in a new tab.
❗If you are an author and publishing to LIVE is deactivated for authors on your tenant, please contact your BRYTER admin directly to publish this Application.
Make Applications available to clients
To make Applications available to clients, ensure that at least one client environment has been created in the Admin Console. In the LIVE environment section, you have the option Make Application available to your clients. Unless you have already published an Application to one or more clients, the sentence will read Not published to [Number] clients.
Select the expand icon to reveal more options. All client environments that have been created will be displayed in the list.
Select one or more client environments that you want to make the Application available to. Then select Apply changes.
Confirm your action by selecting the Confirm changes button.
The section changes to a read-only view. Client environments are now grouped depending on their publishing status. All Application components are now available to the client environment(s) you have previously selected. The Application can be accessed and shared by selecting the link displayed next to the client environment name.
Make Applications unavailable to clients
To make Applications unavailable to clients, expand the client section by selecting the expand icon.
Select Edit to exit out of the read-only view and make amendments.
Then, uncheck one or more client environment(s) and select Apply changes. Confirm your action by selecting Confirm changes.
The section changes to a read-only view. The now-unchecked client environment(s) will be displayed as Not published. There no longer is a link to access and share the Application next to the client environment name. All Application components are no longer available to the previously deselected client environment(s).
Unpublish Applications from Test and Live
Unpublish an Application from TEST
Accessing the context menu allows you to Copy Test Link and Unpublish an Application. Select the three dots icon [ ... ] to access the context menu. Then, select Unpublish and confirm the action by selecting Unpublish in the popup window.
The default TEST environment will return to its unpublished state and the Publish to Test button is now displayed.
Unpublish an Application from LIVE
Accessing the context menu allows you to Copy Live Link and Unpublish an Application. Select the three dots icon [ ... ] to access the context menu. Then, select Unpublish and confirm the action by selecting Unpublish in the popup window.
❗Please note that Applications can only be unpublished from LIVE if they have not been made available to clients at that time.
The default LIVE environment will return to its unpublished state and the Publish to Live button is now displayed.
Unpublish an Application from LIVE not allowed if made available for clients
If the Application is made available to clients, the Unpublish option for the default LIVE environment will be disabled.
Disable Multi-client Publishing on my tenant
If needed, the visible client environments section and access to published Applications by clients can be quickly disabled.
As an admin, simply access the Admin Console and deactivate the respective client environment by selecting Configure, then the red Deactivate button. A popup window will appear where you will be asked to type the display name to confirm deactivation. All users will lose access to any previously published Application components in this particular environment.
Please contact your Customer Success Manager for further information on upgrades, and Integrations and Case Databases within environments, or questions on passwords and access rights.