Admins and module authors can restrict access to published modules on the Test and Live environment directly within the Publishing Settings. The different environments can also have different sets of allowed users. For example, test versions of a module could be made accessible to a specific audience such as internal testers whereas Live environments are restricted to selected external users, e.g., some end-users at your client's organization. Note that these users require specific personalized user accounts that can be added in the Admin Console.
A step-by-step guide to adjusting access settings in the publishing settings
In this step-by-step guide, we will adjust the access settings for the Live environment. The procedure for the test environment is almost identical and can be followed accordingly.
1. In your module, select '🚀 Publish'.
2. Click 'Publish to test' to change from the Development environment to the Test environment. A pop-up window with additional configuration options will appear. Once again, click 'Publish to test'.
3. Then, select 'Publish to live'. Another pop-up window will appear. Adjust the settings as follows:
4. Under 'Access Settings', select 'Only accessible after login'. This will reveal the stricter 'Only accessible for certain users' setting.
5. Now, click 'Only accessible for certain users'. The button 'Select users' is faded and cannot be enabled at this point, as users can only be added after the module has been published to live
6. Select 'Publish to live' to change from the Test environment to the Live environment.
7. Now that your module has been published to Live, go back to the publishing settings and click '...' to access the dropdown menu.
8. Select '⚙️ Live Settings'. The pop-up from step 3 will appear. The 'Select users' button is now enabled and can be used to allow users to access your published Live module.
9. Add users that exist in your organization by typing or pasting their email addresses and confirming through selecting the '+ Add user' button. They will appear under 'Users added' and can, if needed, be removed by clicking '🗑️' next to their name.
💡 If a warning message is displayed, this means that the email address cannot be attributed to an existing author or user account in your organization. Follow the steps below to add new user accounts in the Admin console.
A step-by-step guide to adding new user accounts in the Admin Console
1. As an admin, access the Admin Console by clicking on your username in the right-hand side corner of your BRYTER Dashboard and selecting 'Admin Console'
2. In the side menu, click '👤 Users' to view the users section.
3. There, you can select '+ New user' to set up a new user account. Type or paste the user's first and last name, their email address, and optionally, set a temporary password. Under 'Role', select 'User'. Unlike admins and authors, users only have front-facing access to modules. While they can use a module, they cannot make changes or amendments, i.e. 'build modules'.
Single sign-on (SSO) with SAML integration
If SSO is enabled on your tenant, these users need to be mapped in your active directory. These users can be added in 'Select internal users' once they activated their user account. Please contact your internal admin for support in adding users to your active directory.
💡 For more guidance on how to set up the SAML integration in Azure AD, please refer to our article ⚙ How to set up single sign-on (SSO) with SAML integration and Azure AD
💡 For more guidance on how to set up the SAML integration in ADFS, please refer to our article Single sign-on (SSO) with SAML integration and Active Directory Federation Services (ADFS)