Roles

Introduction

Roles define a set of permissions and the level of access granted for a user to access your application or modify its data. You can define the scopes and access permissions for certain Catalyst components to each role, and assign a role to every user. This categorization enables the users of your application to only access functionalities that are relevant to them.

Roles currently apply to the Data Store and the File Store. You can define the scopes and permissions of each table for each user role in the Data Store. These scopes and permissions also apply to Search and ZCQL by extension, since these components are tied closely to the Data Store. Similarly, you can define Folder access permissions for each role in the File Store.

Roles is available as a section of the User Management feature in Authentication.

Two roles are present by default:

  1. App Administrator: The users assigned to the App Administrator role essentially have an admin access to the application by default. You can override this and define their access levels to the tables in the Data Store and to the folders in the File Store.

  2. App User: The users assigned to the App User role essentially have an end-user level access to the application by default. You can also override this and define their access levels in the Data Store and the File Store.

Note: The App User role is considered to be the default role. When you create a custom role and do not specify the scopes of the role it needs to follow, the scopes of the App User role will apply to the custom role.

In addition to these roles, you can create your own custom roles and define their permissions. You can also make these custom roles as default roles. When a user role is set as the default role, the users who are added to your application are assigned to that role automatically, and the permissions that have been set for that role are made available to them.


Last Updated 2023-05-08 18:05:05 +0530 +0530

ON THIS PAGE