Browse articles
Decide who gets into one project
Add a pool to a project to grant its members access, then set each person's project role to decide exactly how much they can do once they're in.
What you'll achieve
Grant a team access to one project by adding their pool, then set a person's project role so they can do exactly as much as they should.
You'll end up with: A pool added to a project so its members have access, with one person's project role set to fit their part in the job.
Two separate questions, two separate controls
"Can this person open Riverside Apartments at all" and "how much can they actually do once they're in" sound like one question, but Monument deliberately treats them as two, on the project's Permissions tab. Getting them mixed up is how projects end up either too locked down for the people who need to work on them, or too open to people who shouldn't be touching the fees.
We'll open the door for the architecture team on Riverside Apartments, then set exactly how far Priya Sharma can go once she's through it.
Pools decide who's in; roles decide how far they get
A pool is your team. Add one to a project and every member gets access at once, you're not adding people one at a time, you're adding the group they belong to. That has a quiet benefit: add Architect today, and the architect who joins the pool next month is automatically in too, with nothing further to configure. The moment a pool is granted access, its members appear under Resolved staff, there's no separate step to add them individually.
A project role decides what they can do once they're there. Access isn't all-or-nothing. The ladder has four rungs: Owner runs the job and can touch everything including fees and costs, Manager sees the money and manages the work without owning it, Member shapes the tasks they're responsible for while fees and costs stay hidden, and Viewer only looks.
Resolved staff is the current list of people included by this project's access rules. It does not explain every permission route, and organisation-level project access can still apply.
Add the team
- 1
Open Riverside Apartments' Permissions tab. It reads Visible to everyone, the default for any project.
- 2
Click Add group, then choose the Architect pool.
- 3
Priya Sharma already appears under Resolved staff, the pool resolved her with no extra step needed.
Set how far she can go
Priya's here to work on tasks, not manage fees, so Member is the right rung for her.
- 1
On Priya's row under Resolved staff, open her role dropdown.
- 2
Set it to Member.
- 3
Click Save. Priya's on Riverside Apartments as a Member, and the rest of Architect comes with her.
The majority of people on a job are Members: they edit what they're responsible for and never see the money. Save Manager and Owner for whoever is actually planning the fees, and reach for Viewer when someone just needs to follow along.
Troubleshooting
- The Add and role controls aren't showing up. Project access controls require both edit mode and an administrator account. Click Edit on the schedule first, then confirm you are an administrator.
- Someone can edit the project despite no pool including them. An organisation-wide role can override project-level access entirely, a Project Manager can edit any project regardless of its pools. If access looks wrong, check the person's account role next, not just this project's pools.
- Removed a pool, but the person still has access. They may still have organisation-wide project access or match another project access rule. Resolved staff confirms current inclusion, but it does not identify the route.
Where this fits next
You've opened a project to a team and set how far one person can go inside it. The companion piece is organisation-wide access: set a person's account role covers how a firm-wide role can override what you've set here on a single project.