Permission model
Map internal and external roles, finance visibility and approval duties. Test both allowed and refused actions.
Data & access
Project access, approvals and record history
Role, assigned projects and record scope decide what a person can see and do. An approval also checks authority and the version being approved.
PO-024 / Approval requestACCESS & AUTHORITY
REQUESTUser + role + project + record
01Assigned projectCHECK
02Allowed operationCHECK
03Approval limitCHECK
04Submitted versionCHECK
Permission checks are evaluated for each action; illustration does not grant access.
Separation of duties
The person who prepares is not the person who approves
Purchasing prepares the order and an authorised approver reviews it under company rules. The same applies to site evidence and inspection, and to preparing and approving payments.
- Every action records the person, the action, the version and the time.
- The contractor’s internal data stays outside external parties’ access.
- The AI assistant uses the same access scope as the person asking.
Deployment checks
Confirm the controls your organisation needs
Data operations
Agree storage, retention, backup, restore and export with the deployment team, and verify the chosen environment.
Integration control
Name the system that holds each original, who manages each connection and how failed transfers are reconciled.
This page describes the product’s control principles. Security evidence, service levels and certifications for a specific deployment are verified during discovery.
Book a demo with your own project data
Send us a sample schedule, work order or payment file. The demo walks through that process in ACMS with your team.