Application roles¶
Every user account carries exactly one application role. It answers a single question — what can this account do in the software? — and it is the only thing standing between a login and the actions it can take.
There are four, and they are cumulative: each one can do everything the one below it can, plus more.
| Role | In one line |
|---|---|
| Reader | Can see everything in the organisation, and change nothing. |
| User | The working role: authors, reviews, approves and signs quality records. |
| Organisation Admin | Everything a User can, plus running the organisation — members, settings, SSO, imports. |
| Organisation Owner | Everything an Admin can, plus granting the Owner role itself. |
You'll use this page when deciding what to give a new starter, an inspector, or a contractor — and when working out why someone is seeing a permission error.
Application role is not the same as workflow role
An application role says what an account can do. A workflow role — Quality, or line manager — says what quality responsibility a person holds, and it is what gates approvals and escalations. The two are set on different records and neither implies the other. See Application roles vs. workflow roles.
Reader¶
A Reader can open every screen their organisation has and read every document, record, training file and signature in it. What they cannot do is change anything.
This is enforced in one place, for every part of the product at once: any request that would alter data is refused, whether it comes from the web interface, the REST API, or a connected AI assistant. There is no screen where a Reader can edit and no token that grants them write access.
The one exception is their own training. A Reader can work through a document or course assigned to them and sign the completion attestation, because consuming and attesting to your own obligations is not producing controlled output — it is the reason the free seat exists. That covers read-and-understood attestations, course completions, and the annual personnel-currency attestation.
It stays that narrow. A Reader cannot raise an attestation against anyone else's record, cannot attest a class as its instructor, and cannot sign anything that is not a training record — being named as a document or record approver does not let a read seat approve it.
Other things a Reader can do, because none of them change quality data:
- Manage their own sign-in — password, passkeys, multi-factor, SSO.
- Create and revoke their own API token (read-only, like their session).
- Connect a read-only AI assistant.
- Run a full data export of the organisation, if they are also an administrator.
Reader is the right role for inspectors and external auditors, for leadership who want visibility without touching records, and for the trained workforce — anyone who must read procedures and attest to them but should never author one.
User¶
The working role, and the right default for most people. A User does the quality work: authors and edits controlled documents, completes records, raises and progresses deviations, runs change controls, completes their own training, and signs.
Their signing power comes from their workflow role and the segregation -of-duties rules, not from being a User — see Electronic signatures. A User with no Quality workflow role still cannot approve a deviation classification.
What a User cannot reach is anything organisation-wide: the member list's management actions, invitations, organisation settings, SSO configuration, data imports, or the validation packages.
Organisation Admin¶
Everything a User can do, plus running the organisation:
- Members — invite people, resend and cancel invitations, change someone's application role, and deactivate an account.
- Organisation settings — the name, which sign-in and signing methods are allowed, the session timeout, and whether the REST API and AI assistant access are switched on.
- Single sign-on — configure and test an identity provider, and enforce it.
- People — merge duplicate person records, and act on behalf of anyone for training purposes rather than only their own reports.
- Data loads and exports — bulk imports, and the full organisation export.
- Reports — the personnel documents report (job descriptions, resumes, annual attestation), on screen and as CSV.
- Recurring task types — define the task types the organisation uses.
- Validation packages — download the qualification evidence for the release you are running.
- Connected AI assistants — see every assistant connected across the organisation, not just their own, and disconnect any of them.
In a small quality unit it is normal for one or two people to hold this.
Organisation Owner¶
Everything an Organisation Admin can do. The difference is narrow and deliberate:
- Only an Owner can grant the Owner role. An Admin can promote someone to Admin, but cannot create another Owner, and cannot promote themselves.
- The last active Owner is protected. QStack refuses to demote or deactivate an organisation's only remaining active Owner. To hand the role over, make someone else an Owner first, then step down.
That guard exists so an organisation cannot lock itself out of its own administration. It mirrors the rule that a tenant must always keep at least one active Quality role holder.
Assign a second Owner early
A single Owner is a single point of failure: if that person leaves without handing over, nobody inside the organisation can grant the role again. Two Owners costs nothing and avoids the support call.
What each role can do¶
| Reader | User | Org Admin | Org Owner | |
|---|---|---|---|---|
| View documents, records, training, signatures | ✅ | ✅ | ✅ | ✅ |
| Search and run reports | ✅ | ✅ | ✅ | ✅ |
| Manage their own sign-in and API token | ✅ | ✅ | ✅ | ✅ |
| Complete and sign their own training | ✅ | ✅ | ✅ | ✅ |
| Author and edit controlled content | — | ✅ | ✅ | ✅ |
| Sign, approve, and progress workflows1 | — | ✅ | ✅ | ✅ |
| Invite members, change roles, deactivate accounts | — | — | ✅ | ✅ |
| Organisation settings and SSO | — | — | ✅ | ✅ |
| Data imports, organisation export, validation packages | — | — | ✅ | ✅ |
| Merge people; personnel report; task types | — | — | ✅ | ✅ |
| Grant the Organisation Owner role | — | — | — | ✅ |
Change someone's role¶
- Go to Admin ▸ Users.
- Open the person whose account you want to change.
- Set the role in the account section and save.
The same screen is where you deactivate an account. Deactivating is preferred over deleting: it blocks sign-in immediately while leaving every signature, training record and approval that person made intact, which is what the audit trail requires.
Roles are per organisation
An account belongs to exactly one organisation and carries one role within it. There is no cross-organisation role, and no way for a member of one organisation to see another's data — that isolation is enforced by the database itself, not by these roles.
When the whole organisation is read-only¶
Two things can make an account read-only regardless of its role:
- The account's role is Reader.
- The organisation's evaluation period has ended. Records stay readable, searchable and exportable, but no new controlled output can be created — and unlike the Reader role this also stops training attestations, because a signature is controlled output and an expired organisation has no licence to produce one.
The error message tells you which of the two applies.
Devmo support accounts
Devmo Solutions staff accounts can administer any organisation, which is how support and incident response work. Such access is audit-trailed like any other. If your quality agreement requires named, time-boxed vendor access, raise it with us — it is a contractual control, not one you configure here.
-
Subject to the workflow role the person holds and to segregation of duties. The application role permits the action; it does not by itself confer the quality authority to approve. ↩