Overview
When you add or edit a project user (see 2.5.19), you set their Role, Permissions and Access. This article explains what each one means.
👤 Roles
Role | Who they usually are on a project |
|---|---|
Project Admin | Project Manager, Senior Engineer, or Quality Head — often set as the approver for a checklist stage |
Inspector | Site Supervisor or Engineer — the Checker for the checklist; can be a contractor's team engineer who raises the RFI |
Auditor | Architect, Structural Designer, Client, or third-party auditor |
Associate | The Contractor (maker team) who are assigned issues |
🔐 Permissions
Location — makes geo-fencing mandatory: the user must be within the project radius to do inspections.
Authentication — the user must authenticate the phone lock before starting an inspection.
🗂️ Access
Web Access — Team or Project:
- Team — the user can view only their team's data. - Project — the user can view all teams' data across the project.
Raise Instruction — allows the user to raise instructions in the mobile app.
Checklist — assign the checklist(s) to the user.
RFI — assign the RFI stage(s) of the checklist to the user.
❓ FAQ
What roles can I give a project user, and who are they? Project Admin (PM/Senior Engineer/Quality Head, often the approver), Inspector (Site Supervisor/Engineer, the Checker, can raise the RFI), Auditor (Architect/Designer/Client/third-party), Associate (Contractor/maker team, assigned issues).
What does the Location permission do? It makes geo-fencing mandatory — the user must be within the project radius to carry out inspections.
What does the Authentication permission do? The user must authenticate the phone lock (fingerprint/passcode/face) before starting an inspection.
What's the difference between Team and Project (Web) access? Team — the user sees only their team's data. Project — the user sees all teams' data across the project.
What does "Raise Instruction" do? It lets the user raise instructions in the mobile app.
What do the Checklist and RFI options do? Checklist assigns the checklist(s) to the user; RFI assigns the RFI stage(s) of the checklist.
💡 Good to know
Roles map to real parties: Project Admin (PM/Quality Head, often approver), Inspector (Checker, raises RFI), Auditor (Architect/Client/3rd-party), Associate (Contractor/maker team, assigned issues).
Location = geo-fencing (within project radius); Authentication = phone-lock check before inspection.
Web Access: Team (own team) vs Project (all teams).
Raise Instruction enables raising issues on mobile; Checklist and RFI assign checklists and RFI stages per user.
🔗 Related articles
2.5.19 How to add or edit a project user
2.5.21 How to bulk-manage users on the Project Users tab?
2.5.13 How to bulk-configure multiple checklists?