Skip to main content
BRYTER Academy

Configure End User Access for Applications

Updated

For each module, data view, and page in your application, as well as for the application itself, you can view and change end user access.

You can select one of these three access levels:

  • Public: Anyone who has the link to the module, data view, or application can access (for some edge cases, see also the warning below).
  • All authenticated users: All users with a BRYTER account in the environment can access when they are logged in. This is the default setting.
  • Specific application role(s): Only logged-in end users with a designated application role that grants permission can access. This setting allows you to provide access to specific groups of people, such as managers. Learn how to create application roles and assign end users to them here.

If you restrict access to specific application roles, make sure to grant yourself the access that you need. Being a collaborator in an application does not automatically give you end user access.

 

Configure end user access to your application

Decide who is allowed to open and access the published application:

  1. On the Build page of your application, go to the column End user access in the top right section and click on the current access level.
  2. In the modal, select your preferred access level in the dropdown below Define who has access.
  3. If you select the access level Application role, a list of application roles displays. Select the ones you want to grant access to. You can select multiple roles that should have access.
  4. Click Save changes.

 

Configure end user access to modules, data views, and pages

Within the application, you can also determine which modules and data views an end user has access to. End users with access rights to the application will then only see those modules, data views, and pages that they have been granted access to.

  1. On the Build page of your application, go to the column End user access in the Modules, data views, and pages section.
  2. Click on the current access level of the module or data view you want to configure.
  3. Select the end user access level like you do for applications.

End users with access rights to a module, data view or page, but not to the application containing them, still can access those modules and data views via direct links.

 

Interplay with other features

Note that Built-in values cannot be used with end user access level Public. If you select Public, referenced built-in values will be empty. They will not display in text. And logic utilizing built-in values might break. The same applies to the placeholder {{current_user_email}} when filtering data views.

 

Occasionally asked questions

How do I preview who can access what?

To test each application role's end user access rights, you can assign yourself – or other test users – in the Test environment to one or several role(s).

The benefits are that you can...

  • test access permissions for a new application, its modules, data views, or pages on the Test environment and be confident that your end users on the Live environment have the proper access,
  • test the Public and Authenticated access without any further configuration – before publishing a module or application,
  • assign yourself to one or several roles on the Test environment and open the module wizards or the application to verify if the access permissions of your application roles are set correctly. If everything works as expected, it will also work in the Live environment.
  • Further, any changes to roles or access are applied immediately to all environments.
What happens with configuring API key access and/or password-protecting modules?

If necessary, you can still restrict access to a module even further with the remaining options of the usual access settings in the editor.

 

Related topics

Related to

Was this article helpful?

0 out of 0 found this helpful
Return to top

Related articles