The right access for every role
Access rules are checked on the server for each request, not only hidden on the screen.
Five levels, from administrator to stores
Each account has one level. Project engineers are also limited to their assigned projects.
| Level | Role | Can open | Can change |
|---|---|---|---|
| 1 | Administrator | Everything, all projects | Everything, including users and backups |
| 2 | Project engineer | All work areas, assigned projects only | Project data on assigned projects |
| 3 | Fabrication shop | Fabrication section | Fabrication fields and material issue |
| 3 | QC | Fabrication section | QC fields, inspections and RIRs |
| 3 | Stores | Material Receiving | Receipts, stores inspection and RFIs |
Built to protect project data
Sign-in protection
Salted, iterated password hashing, temporary lockout after repeated wrong passwords, and a required password change after an account is issued.
Commercial data stays private
Fabrication, QC and Stores accounts receive only the project data they need. Budgets, cashflow and prices are not sent to them.
Traceability
An activity log records who changed what, and the administrator can review the sign-in history.
Automatic backups
A copy of project, vessel and piping data is taken before the first change each day and kept for 30 days.
Deleted is not destroyed
Deleted projects, vessels and attachments are moved to a separate folder on the server, not erased, so they can be recovered.
Safe when people overlap
When two people save at once, their changes are merged. If both change the same field, the person saving last is warned to check it.
See EPC Thread on a project like yours
Tell us how your projects run and we will walk you through the system.