Permissions Guide
Complete reference of the Modunex permission architecture. Explains how permissions are structured, combined, and inherited to control access to each module.
Complete reference of the Modunex permission architecture. It explains how permissions are structured, combined, and inherited to control access to each module of the platform.
For: Company Administrators · IT · Security Managers
Permission Architecture
The permission model is built on modules, access levels, and inheritance layers. For each module, a user is granted one of four access levels:
- None — no access to the module at all.
- View — read-only access; the user can see information but not modify it.
- Collaboration — read and write access; the user can create, edit, and collaborate.
- Admin — full control, including the module's settings and its users.
Company Permissions
Permissions configured at the company level that apply by default to all projects.
Project Permissions
Permissions specific to a project that can override the company ones.
Role Based Permissions
Permissions assigned to a role (e.g., Project Manager) that apply to all users with that role.
User Based Permissions
Permissions assigned directly to an individual user, with higher priority than the role's.
Permission Inheritance
When permissions exist at company, project, role, and user level for the same module, the conflict is resolved by priority.
Priority order (lowest to highest): Company defaults → Role permissions → Project permissions → User overrides.