"Permission denied" or greyed-out actions
If a button is missing, greyed out, or you see a “permission denied” message, DASH is applying role-based access. The controls you see depend on your role — this is by design, not a fault.
Why an action is unavailable
Section titled “Why an action is unavailable”Every action is gated by a permission area (Organisations, Materials, Definitions, Definition Maps, Certificates, Sign & Submit, Account Admin) combined with an operation (Create, Read, Update, Delete). Your role grants a specific grid across those areas. If your role doesn’t include the operation for that area, the matching control is hidden or disabled — so different people see different menus.
Who can do what
Section titled “Who can do what”| You want to… | You need… |
|---|---|
| Sign a certificate and submit it | Sign & Submit — only Quality Person, Admin or Account Owner |
| Create or edit definitions and maps | Definitions / Definition Maps update — typically Technician, Admin, Owner |
| Create and prepare certificates | Certificates create — Submission Coordinator, QP, Admin, Owner |
| Set up Materials, channels and Organisations | Materials / Organisations — Project Manager, Admin, Owner |
| Invite users, change roles, manage the account | Account Admin — only Admin or Account Owner |
Get the access you need
Section titled “Get the access you need”- Confirm which action you’re missing and which permission area it belongs to (the table above helps).
- If it’s genuinely part of your job, ask an Admin or the Account Owner to grant you the role — only they can change roles.
- If a one-off task needs a higher permission (like signing), the simplest path is to hand the record to someone who already holds it rather than changing your role.
See Team management for how administrators invite users and set roles.