Roles

A Role defines a category of user access. Roles carry two system-level flags that control what parts of the platform a user can access, and can be organised into a hierarchy using a Parent Role. Roles are assigned to users through Identities.

The Roles screen

Navigate to Security - Roles to see all roles in the current application:

Column	Description
Role Name	Human-readable name
Role ID	Unique identifier
Role Description	Optional description of what the role represents
Is Security Administrator	Whether this role can manage identities (user accounts)
Is System Designer	Whether this role can design applications in the Designer
Parent Role Name	The parent role this role inherits from, if any

Predefined roles

Four roles are built into every application and cannot be modified or deleted:

Role	Security Administrator	System Designer	Description
Administrator	Yes	Yes	Can execute all functions and view all data
Regular User	No	No	Cannot modify the system, but can enter data
Security Administrator	Yes	No	Can manage identities
System Designer	No	Yes	Can design applications in the Designer

Creating a role

Clicking + Add Role opens the Add Role panel:

Field	Description
Role Name	Human-readable name
Role ID	Auto-generated from the name
Role Description	Optional free text describing what the role represents
Parent Role	Optional - assigns this role a parent in the role hierarchy. A role inherits the access of its parent.
Is Security Administrator	When checked, users with this role can manage Identities
Is System Designer	When checked, users with this role can access the Designer to build and modify applications

Where roles go from here

Roles are assigned to users through Identities. Once assigned, a role is available as a Role dimension in security rules on navigation items, Database Workflows, Server Functions, and other resources that support access control.