Roles and permissions
Controlling who can do what, down to individual fields.
Roles gather permissions; users are assigned roles. Permissions reach beyond modules down to individual field groups, and can vary by lifecycle state.
Module permissions
For each module a role can have no access, read, edit, or full control including delete.
Field-level permissions
Fields are grouped — identity, engineering, supply chain, quality, compliance, manufacturing — and each group can be permitted per role and per lifecycle state. This is what allows a policy like:
- In WIP, engineering can edit everything
- In Released, engineering fields lock behind a change order
- But supply chain and quality fields stay editable in Released, because a price update isn't a design change
What users see
A field somebody can't edit renders read-only with the reason on hover, rather than appearing editable and then refusing to save.
Every edit writes to the audit trail regardless of role, including edits by administrators.
Email [email protected] and a person will pick it up. Include the part number and what you were doing — it saves a round trip.