Troubleshooting RBAC

RBAC (role-based access control) controls what end-users can see and do in an application. Set up RBAC at the environment, module, and component level. Use the Express Preview Bar in Express View to test and troubleshoot RBAC settings.

Test RBAC in the following situations:

• Permissions were changed and each role's experience needs verification.

• An end-user reports being unable to view a page their role permits.

• The module has sensitive information that only certain roles should see.

Testing RBAC in the Module Builder

RBAC lets you adjust permissions for different parts of an application. After configuring RBAC settings, test the experience for each role directly in the Module Builder using the Preview As feature.

To test a role's view:

1. In the Module Builder, select UI View from the view selector at the top.

2. At the far right of the toolbar, click the Show Runtime Toolbar icon.

3. At the top right of the UI preview, click the Show tab.

4. From the Preview As drop-down, select a role. The preview updates to display the module through that role's perspective.

The Preview As drop-down defaults to the Administrator role, which has full access; every component is visible and interactive. When a different role is selected, the preview displays only what that role is permitted to access.

If a role's preview experience does not match expectations, the RBAC settings likely contain an error. Check RBAC settings at the component, module, and environment level, then preview again through that role.

If the Runtime Toolbar is not available, confirm the Express Preview Bar is enabled in Environment Administration. If it remains unavailable, use the test user account approach described below.

Testing RBAC Settings with a Test User Account

Another approach is to create a test user account. Creating a test user account in Unqork requires a unique email address. With Gmail or Outlook, adding a plus sign and a unique string before the @ sign creates an alias that delivers to the main inbox. For example, if the email address is nocodeisfun@unqork.com, use nocodeisfun+test@unqork.com as the test account address.

After creating the test account, assign the account a role in Unqork administration. Log in as the test user and navigate through the module; the experience reflects only what that role is permitted to access. Create additional test accounts for each role that requires verification.