How to test team permissions in a construction ERP
Test allowed and forbidden actions with separate accounts, not just menu visibility.
By ENRO team
Test ERP permissions using separate role accounts and records in more than one project. A hidden menu does not prove access is blocked, and a role name does not prove what the person can do.
Set up a small permission matrix
Use sample records in Project A and Project B. Define the intended outcome for each action before testing. For example, a Site Manager assigned only to A may be allowed to create an A site update, while being unable to read B's records. The exact policy is the company's decision, not a universal rule for every Site Manager.
Suggested actions include viewing a record, creating a draft, editing an existing record, approving, exporting, changing assignments and using AI with that record as context.
Check both positive and negative cases
- The assigned user can perform the allowed A action.
- The same user cannot open B through a copied record link.
- Search, lists, totals and exports do not disclose B.
- AI answers respect the same project boundary.
- A finance approval cannot be performed by a role lacking that authority.
- A removed or suspended member loses access as the product's policy specifies.
Run these checks only in an authorized workspace with test accounts. Do not probe other customers' records or guess their identifiers.
Record evidence and expected results
For each check, keep role, project assignment, action, expected result, actual result, time and a sample record reference. A test that says permissions work without these details is hard to repeat after a change.
If access is too broad, restrict the affected workflow while the responsible team investigates. Avoid compensating with a written instruction telling users not to click the exposed link.
Repeat the relevant checks when roles, membership, export behavior or AI tools change. The goal is the same business boundary across every way a person can read or change information.