---
title: "Roles and permissions"
space: "BuildSuite Core"
url: "https://wiki.buildsuite.io/core/introduction/roles-and-permissions"
updated: "2026-11-16"
---

What a user can see and do in BuildSuite comes from their **persona**. Each persona grants a set of Frappe roles, and each role has permissions on each workspace and document. Being on a project’s team doesn’t change what a user can access.

### How access is set

1. An admin gives each user a **persona** in **Settings → Users**.
2. The persona grants its **roles** (set in **Settings → Personas**).
3. Each role’s **permissions** decide which workspaces, lists, records and buttons the user sees. The defaults are shipped with BuildSuite, and admins can change them in Frappe Desk.

### Personas


| Persona                      | Typical work                                               |
| ---------------------------- | ---------------------------------------------------------- |
| **Director / Owner**         | Oversees all projects, approves high-value items           |
| **Project Manager**          | Runs projects, approves stages, SCOs and material requests |
| **Estimator**                | Rate Master, assemblies and BOQs                           |
| **Quantity Surveyor**        | BOQs, measurements and certification                       |
| **Site Engineer**            | Tasks, progress, material requests, measurements           |
| **Foreman / Supervisor**     | Crews, attendance, daily progress                          |
| **Procurement Officer**      | Purchase orders and suppliers                              |
| **Store Keeper**             | Receipts, consumption and site stock                       |
| **Accountant**               | Invoices, bills, payments, petty cash and expenses         |
| **HR Manager**               | Field employees and attendance                             |
| **BuildSuite Administrator** | BuildSuite settings and users                              |
| **System Manager (Admin)**   | Everything, including Frappe Desk                          |


### Workspace access by role


| Role                 | Site Execution | Estimation | Procurement    | Subcontract             | Workforce | Equipment | Project Finance |
| -------------------- | -------------- | ---------- | -------------- | ----------------------- | --------- | --------- | --------------- |
| Director / Owner     | Full           | Full       | Full           | Full                    | Full      | Full      | Full            |
| Project Manager      | Full           | Read       | Approve        | Approve                 | Approve   | Approve   | Full            |
| Estimator            | Read           | Full       | –              | Read                    | –         | –         | Own records     |
| Quantity Surveyor    | Read           | Full       | –              | Full                    | –         | –         | Read            |
| Site Engineer        | Full           | –          | Raise requests | Read + own measurements | Full      | Full      | Own records     |
| Foreman / Supervisor | Own records    | –          | –              | –                       | Full      | Full      | Own records     |
| Procurement Officer  | –              | –          | Full           | Full                    | –         | Full      | Own records     |
| Store Keeper         | –              | –          | Full           | –                       | –         | Full      | Own records     |
| Accountant           | Read           | –          | Read           | Pay                     | Pay       | Read      | Full            |
| HR Manager           | –              | –          | –              | –                       | Full      | –         | Own records     |
| System Manager       | Full           | Full       | Full           | Full                    | Full      | Full      | Full            |


**Own records** means the user can create and see their own petty cash requests and expenses.



### Edit role permissions

The shipped permissions are a starting point. Admins can change what each role can do.

1. Open **Frappe Desk → Role Permissions Manager**.
2. Select the **Document Type** (for example *Purchase Order*) or the **Role** (for example *BuildSuite Site Engineer*).
3. Tick or untick the permissions you need: **Read**, **Write**, **Create**, **Delete**, **Submit**, **Cancel**, **Amend**, **Print**, **Export** and **Report**.
4. Use **If Owner** to let a role see only the records it created, for example its own expenses.
5. Save. The change applies the next time the user loads the page.

> **Note:** App updates don’t reset your permission changes. To bring the defaults back, use **Settings → BuildSuite Core Settings → Restore defaults**. This overwrites all your changes and **can’t be undone**, so click **Export permissions** first to keep a copy.

> **Tip:** To change what a whole group of users can do, edit the **role**. To change one user’s access, give them a different **persona** in **Settings → Users**.

### Approvals

These documents need approval before they take effect. The approver is set by the document’s workflow.


| Document                | Approved by                                                         |
| ----------------------- | ------------------------------------------------------------------- |
| Material Request        | Project Manager                                                     |
| Stage Planning          | The project’s **Approval Required Role** (default: Project Manager) |
| Scope Change Order      | Project Manager / Director                                          |
| BOQ revision            | Project Manager / Director                                          |
| Petty Cash              | Accountant (disbursement)                                           |
| Subcontractor (RA) Bill | Per workflow                                                        |




### Change an approval flow

Approvals (Material Request, Stage Planning, SCO, BOQ revision, Petty Cash and RA Bill) are Frappe **Workflows**. Admins can change who approves, add or remove steps, or switch a workflow off.

1. Open **Frappe Desk → Workflow** and open the workflow, for example *Material Request*.
2. Under **States**, set each state (for example *Pending PM Approval*, *Approved*, *Rejected*) and the **role allowed to edit** the document in that state.
3. Under **Transitions**, set each action (for example *Approve*, *Reject*), the state it moves from and to, and the **Allowed** role that can take it. Add a **Condition** if needed, for example an extra approval above a certain value.
4. Tick **Is Active** to use the workflow, or untick it to switch approval off for that document.
5. Save. New and pending documents follow the new flow.

> *Example:* To have material requests above ₹1,00,000 approved by the Director as well as the PM, add a state *Pending Director Approval*. Then add a transition from *Approved by PM* to it, with a condition such as `doc.grand_total > 100000` and **Allowed** set to *BuildSuite Director*.

> **Caution:** Documents that are already partway through a workflow keep their current state. Test workflow changes on your test site first. If you change a state’s name, any record in that state gets stuck until you move it on by hand.

> **Note:** **Settings → BuildSuite Core Settings → Set up app data** reinstalls only workflows that are **missing**. It doesn’t overwrite workflows you’ve edited.

### Frequently asked questions

**Does adding someone to a project team give them access to it?**  
No. Access comes from the user’s persona and role permissions only. The team records who does what on the project.

**Why can’t I see a button someone else can?**  
Buttons appear only for roles allowed to use them. Ask your admin to check your persona.