Roles
Roles define groups of users who share responsibilities in a Protrak application. Administrators use roles to control who can see pages and widgets, create records, work in lifecycle states, perform promote actions, run reports, and participate in configured business rules.
Use roles when access or user experience should follow a responsibility model, such as Administrator, Manager, Reviewer, Field User, Supplier, Customer, or Process Owner.
What roles control
| Area | How roles are used |
|---|---|
| Type access | Control which roles can create instances of a type or use the type in reports. |
| Lifecycle permissions | Control what users can view, edit, link, unlink, delete, or promote in each lifecycle state. |
| Promote actions | Restrict transitions such as Submit, Approve, Reject, Complete, or Reopen to the roles responsible for them. |
| Design Studio visibility | Show page templates, forms, containers, and widgets only to selected roles. |
| Rules and access policies | Evaluate the current user's roles when deciding whether something is visible, required, or accessible. |
| Programs and notifications | Find users by role, assign or remove roles, and send notifications to role-based recipients. |
| Role Configuration Guide | Follow the end-to-end steps to create a role, assign users, configure access, and validate role-based experiences. |
Guidance
- Name roles after responsibilities, not individual people.
- Keep role sets simple; use lifecycle permissions, rules, or access policies for context-specific behavior.
- Validate both allowed and restricted experiences after changing role assignments.
- Review templates, widgets, lifecycle actions, rules, access policies, notifications, and programs before renaming or removing a role.