Roles and permissions
What owners, admins, users, auditors and viewers can do, and the Product assurance roles.
Each person has one quality management role in each organisation they belong to. If your organisation uses Product assurance, people can also hold a Product assurance role. The two are separate.
Quality management roles
| Role | Can | Paid? |
|---|---|---|
| Owner | Everything, including billing, removing all of a module's data and deleting the organisation's records. An organisation always has at least one owner. | Yes |
| Admin | Everything except owner-only actions: manage members and invitations, settings, locks and approvals, delete records, API keys. | Yes |
| Auditor | Carry out audits and record findings, and work on records like a user. | Yes |
| User | Create and update records day to day: NCRs, CARs, actions, complaints, inspections, risks and so on. | Yes |
| Viewer | See everything in the organisation and export it. Change nothing. | Free |
Some actions are limited to owners and admins even though users can edit the record, for example locking a completed audit and deleting evidence attached to a quality record.
Product assurance roles
| Role | Can |
|---|---|
| Administrator | Create, change and delete products, configurations, components, claims, evidence links, publications, changes and reviews. |
| Technical approver | Create and change product records and conclude technical reviews. Can't delete. |
| Read-only | See product assurance records. Change nothing. |
Someone with no Product assurance role can't see product records at all, or the links, history and conversations about them. A person who is a viewer for quality but holds an administrator or technical approver role in Product assurance counts as a paid user.
Decisions reserved for people
Whatever the role, some things are only ever done by a person, in Doctilla, through a control made for it. They can't be done by AI, and most can't be done through the API either:
- closing a CAR, completing an 8D step and recording whether a fix worked;
- setting a supplier's status and an evaluation's outcome, and an objective's status;
- approving a document revision, management review minutes or a concession;
- accepting a mapping to a standard, and marking a claim as supported;
- concluding a technical review and approving a product change.
The full list for integrations is in the API reference.
How permissions are enforced
Permissions are enforced by the database, using row-level security on every table, not just by hiding buttons. The same rules apply whether someone uses the app, an API key or an AI assistant. Doctilla only shows a control to people the database will let use it.