Roles and Permissions
Project Management access is dynamic. The module does not rely on one fixed role matrix.
Permission layers
Section titled “Permission layers”| Layer | Controls |
|---|---|
| Navigation permissions | Which PM pages appear or can be opened. |
| Django model permissions | Broad backend capabilities such as viewing, creating, assigning, approving, exporting, or managing workflows. |
| Deep page permissions | Sections, fields, buttons, row actions, and data scope per page. |
| Workflow action permissions | Which workflow transition actions a designation can perform. |
| Data scope | Which records are included in list/query results. |
Data scopes
Section titled “Data scopes”| Scope | Meaning |
|---|---|
own |
User’s own assigned/created records. |
team |
Team-level records. |
department |
Department-level records. |
all |
All permitted organization records. |
Common PM model permissions
Section titled “Common PM model permissions”Project permissions include view all, view team, view own, create project, assign project, approve project, submit project, request extension, export projects, view/edit budget, view quality or performance score, meeting permissions, and manage project workflow.
Task permissions include view all tasks, view team tasks, assign task, approve task, bulk task actions, and view task timelog.
Why buttons disappear
Section titled “Why buttons disappear”A button can be hidden because:
- The user cannot access the page.
- The section is hidden by deep permissions.
- The row action is disabled.
- The field needed for the action is hidden.
- The workflow transition is not valid from the current state.
- The user lacks workflow action permission.
- The record is outside the user’s data scope.