People & Access Example
Decide who can read, write, review and publish.
Available when this feature is connected.
Cross-app access is a planned integration. Today this table is an example of how access would look side by side.
People and what they can do (5)
Fictional people with an access level for each product. Nothing here can be changed.
| SOP | LMS | FSQ | |||
|---|---|---|---|---|---|
|
Pat Example Team Member
|
Bakery Plant 1 | Read | Read | Read | |
|
Drew Demo Procedure Author
|
Sauce Plant A | Write | Read | Read | |
|
Quinn Sample Reviewer
|
Sauce Plant A | Review | Read | Review | |
|
Sage Placeholder Manager
|
Bakery Plant 1 | Review | Write | Write | |
|
Robin Fictional Account Administrator
|
Bakery Plant 1 | Admin | Admin | Admin |
No people have been added yet.
All example rows are shown on this page.
What the levels mean in SOP
- Read Can open and read released procedures.
- Write Can also create and edit drafts.
- Review Can also check proposed changes and ask for corrections.
- Admin Can also manage settings and release procedures.
Go to Library Setup
Next: choose numbering, tags and departments.