Documentation ยท OpsDocs
Opsdocs Setup Overview
What this does
This overview explains what needs to be in place before OpsDocs works properly for staff access, required reading, and document administration.
What must already be set up
- the company must have an active
OpsDocssubscription - the user must be assigned access to
OpsDocs - the surrounding user and staff structure should already exist in the
Admin App
Why the Admin App matters here
If a staff member cannot access OpsDocs, or the wrong people are being prepared for document workflows, the first checks often live in the Admin App.
That matters because app access and the surrounding user setup are not managed inside OpsDocs itself.
What you can set up inside OpsDocs
Once shared setup is in place, OpsDocs has its own app-specific surfaces such as:
- document access
- required reading
- acknowledged documents
- admin document management
- compliance dashboard
- document list settings
- permissions
Recommended setup order
- Finish the shared user and access setup in the
Admin App. - Assign the right people access to
OpsDocs. - Configure document lists and permissions.
- Add documents and required reading flows.
What stays incomplete if skipped
If app assignment is missing, users may not be able to access OpsDocs.
If the surrounding user setup is incomplete, document visibility and acknowledgment workflows may not reach the right people.