Navigation
CONCEPTS
Roles & permissions
How Decimal's role-based access control works
Overview
Decimal uses a role-based access control (RBAC) system to ensure users can only access the features and data relevant to their responsibilities. Each user is assigned a single role that determines their permissions.
Role hierarchy
Super Admin
├── Principal
│ ├── Teacher
│ ├── Finance Officer
│ ├── Secretary
│ └── Admissions Officer
└── Parent
- Super Admin: Platform-wide access across all schools
- Principal: Full school-level access
- Staff roles: Scoped to their specific responsibilities
- Parent: Read-only access to their child's data
Permission model
Permissions are defined at the module level. Each role has a set of allowed actions (create, read, update, delete) for each module:
| Module | Teacher | Finance | Secretary | Principal |
|---|---|---|---|---|
| Students | Read (assigned) | Read | Full CRUD | Full CRUD |
| Attendance | Create/Edit (assigned) | Read | Read | Full CRUD |
| Grades | Create/Edit (assigned) | None | Read | Full CRUD |
| Finance | None | Full CRUD | Read | Full CRUD |
| Settings | None | None | None | Full CRUD |
Customization
While Decimal ships with predefined roles, the super admin can fine-tune permissions for each role from Settings → Permissions. This allows schools to adjust access levels to match their specific organizational structure.