Roles Policy
Roles Policy
Dossira roles are technical access levels. They are not professional titles and they do not create board-specific, client-specific or transaction-specific duties.
Supported role labels
The current backend role labels are:
| Level | Label |
|---|---|
| 0 | Viewer |
| 1 | Submitter |
| 2 | Contributor |
| 3 | Room editor |
| 4 | Manager |
| 5 | Admin |
| 6 | Super admin |
There is no separate backend Owner role. If your internal policy uses “owner” as a business responsibility, record that outside Dossira and assign the Dossira technical role that exposes the needed product actions.
Practical policy
- Give persistent member access only to people who need to work inside the room.
- Use lower roles where read access is enough.
- Use higher roles only for people who should manage room membership or settings.
- Treat pending account invitations as pending; they are not accepted room members.
- Use selected external shares instead of membership when someone only needs specific files.
Changing or removing a member prevents future use through the normal product path after the system processes the change. It does not prove that downloaded files were recovered, and public documentation must not promise immediate backend cache revocation.
Record approvals elsewhere
Dossira does not currently provide a complete customer-facing membership-change audit export. Record access approvals, role changes and offboarding decisions in the system and procedure approved by your organisation.