User roles and permissions
In codeto report, each role only sees and does what is intended for its task.
Two views of the same thing
- Day-to-day roles: employees, project managers, supervisors, masters, admins.
- Technical roles: SU, FA, RW for permission checks in the system.
Day-to-day roles
Employees
- Record working times and absences.
- Enter additions (expenses, kilometres etc.).
- Request absences.
Project managers
- Check the hours on their projects.
- Approve or reject project hours.
Supervisors
- Check the team's weekly reports.
- Approve or reject reports/absences.
- React to rule violations.
Masters
- Overview of all employees in the company.
- Manage company settings (supplements, public holidays, default working times).
- See open, missing and unapproved reports across the company.
- Can intervene in the process: record reports on behalf of someone, approve/reject on behalf, reopen closed weeks.
Administrators
- Full overview of all companies in the group.
- Open new companies in codeto report.
- Manage group-wide absences.
- Like masters, may intervene in reporting and approval processes.
Technical roles
- SU (Super User): full access, also across multiple companies. Mainly intended for groups with several companies, so that one person can access all of them. May close/reopen weeks at any time and override approvals.
- FA (Full Access): nearly full access within their own company, may close/reopen weeks and usually override approvals.
- RW (Read/Write): write permissions for own reports, no closing/administration rights.
Permission matrix
| Area | SU | FA | RW |
|---|---|---|---|
| Record/edit own reports | Yes | Yes | Yes |
| Approve/reject reports | Yes | Yes | Only if recipient |
| Close/reopen weeks (incl. others') | Yes | Yes | No |
| Company/group settings | Yes (all) | Yes (own company) | No |
tip
Project managers and supervisors are often additionally listed as recipients in the approval structure. This allows them to approve and reject reports.