Configuration and Settings
Partially availableSet up your company, users, roles, and reference libraries without uncontrolled document sprawl.
The operational problem it solves
Company details, user access, and reference documents are scattered, and granting or revoking access depends on whoever set things up originally.
Who uses it
- Company administrators
- QA managers
When it is used
Used at setup and whenever company details, users, roles, or libraries change.
What information goes into it
- Company information (name, contact, address, timezone, default currency)
- User accounts and roles
- Documents (SOPs, inspection templates, compliance references)
What the user can do
- Maintain company settings used across records
- Invite users and assign admin or user roles
- Manage who can administer the platform
- Store version-numbered reference documents in a document library
Validation and permission checks
- Administrative actions require an admin-role account
- User invitations and settings changes are audited
- Tenant-level separation keeps each organization's records scoped
Statuses you will see
- Admin-only
- Administrative actions require an admin-role account.
How information moves through this module
- 01
Input
Approved scope and records arrive
- 02
User action
Maintain company settings used across records
- 03
Validation
Administrative actions require an admin-role account
- 04
Output
The module's recorded outcome
- 05
Next step
Handed to Work Requests
What it produces, and where it goes next
A governed operational foundation: your company, your users, your libraries.
Limitations and prerequisites
A visual workflow designer, configurable validation rules, and customer-specific report templates are planned. Today configuration covers settings, users, roles, tenants, and document libraries.
Module questions
Synthetic preview data shown for illustration.
See Configuration and Settings in action
A demonstration uses synthetic data and walks through this module against your own company's workflow.
Book a demo