Roles and Permissions¶

This page summarizes practical access expectations used across the platform.

Role Model (Typical)¶

• Viewer: read-only access for scoped project data.
• Contributor/Editor: create and update operations in assigned modules.
• Lead/Admin: governance actions such as freeze, approval, lock or unlock, and configuration controls.

Permission Patterns¶

flowchart TD
    A[User Login] --> B[Project Context Selected]
    B --> C[Role Resolution]
    C --> D[Read and write checks in views]
    D --> E[Action allowed or blocked]

Guidance by Action Type¶

• CRUD actions should enforce project-aware permission checks.
• Governance actions should require elevated role checks.
• Bulk actions should preserve auditability and explicit user feedback.