Administration
Define the admin-level access model for ProductionOps360. These settings are the policy layer for approvals, document control, and who can change system setup.
Keep integration setup, document mapping, and workflow defaults restricted to admin roles.
Active permission context
Checking user...
Role
Unknown
Disabled modules disappear for everyone and cannot be opened. Development modules start switched off until they are ready.
Map real users to roles. Email matching is case-insensitive and is enforced by the API routes.
Add group names from your identity provider, or comma-separated member emails, then map them to a role.
| Role | Purpose | Admin settings | Approve POs | Approve bills | Manage documents | Edit stages | Manage logistics | Venue Crew | Mission Control views | Actions |
|---|---|---|---|---|---|---|---|---|---|---|
| Built in | ||||||||||
| Built in | ||||||||||
| Built in | ||||||||||
| Built in |
These roles now drive server-side checks for settings changes, supplier cost approvals, bill approval stages, commercial stage edits, SharePoint document uploads, and the Mission Control views each person can open.