Role
Roles are object types used to group permissions and assign work to users in a Lowgile application.
They are created in the Design area and then referenced throughout the application by workflows, screens, and access control configurations.
- Path: Design → Object types → Role
When to use roles
Section titled “When to use roles”Use roles when you need to:
- Assign tasks in a workflow (e.g. Requester, Approver),
- Control which users can access specific features, or
- Group users by responsibility or function.
How roles are used
Section titled “How roles are used”Roles are used in Lowgile in the following ways:
1. Workflow assignment
Section titled “1. Workflow assignment”Roles are used to assign tasks to the correct users in a process.
For example:
- A Requester submits a request.
- An Approver reviews and approves or rejects it.
In process diagrams, roles are typically assigned to swimlanes.
2. Access control
Section titled “2. Access control”Roles are used to apply permission sets to users.
They determine:
- Which screens a user can access,
- Which actions they can perform, and
- Which data they can view or modify.
Accessing roles in expressions
Section titled “Accessing roles in expressions”Roles can be referenced in expressions using:
This.$RolesThis provides access to the set of roles available in the application.
Naming conventions
Section titled “Naming conventions”Use clear, functional names that reflect responsibility:
RequesterApproverProcurementFinance
Avoid overly technical or ambiguous names.
Key Lesson
Roles are simple by design. Define them once, then reuse them across workflows and access control to keep your application consistent.