Browse articles
- Getting started
- Project finances
- Billing by the hour
- Practice finances
- Grouping fees
- Budgeting project costs
- Claim an expense
- Recording revenue entries
- Recording project expenses
- Purchase orders
- Approving expenses
- Going further
- Construction cost fees
- Recurring fees
- Billing expenses
- Contingencies and discounts
- Billing progress claims
- Project templates
- Overheads
- Getting started
- Billing milestones
- Sending an invoice
- Billing logged time
- Month-end invoicing
- Fee proposal templates
- Writing a fee proposal
- Getting a proposal signed
- Link invoices that are already in Xero
- Going further
- Payments and overdue invoices
- Connect your accounting system
- Fee groups on invoices
- Tax codes and accounts
How permissions work
Understand Account, Project, and Team access levels, where defaults apply, and why a visible level may still be limited.
What you'll achieve
Choose an access level and understand the access it will give a person.
You'll end up with: You can set account, project, and team access in the right place and check the effective result.
Monument uses three kinds of access level. Each answers a different question.
| Access level | What it controls | Where you define it |
|---|---|---|
| Account | What a person can do across the practice: finances and rates, projects, team management, practice reports, records, invoices, expenses, time and admin jobs. | Team › Access levels, Access levels section |
| Project | What they can see or change on a project or task branch: Revenue, Expenses, Milestones, Contacts, Tasks, Resources, Time, Budget usage, and Practice targets. | Team › Access levels, Project roles section |
| Team | Which colleagues' profiles, time, leave, and schedule they can work with. | Team › Access levels, Team roles section |
You define an access level once on the Access levels page (Team › Access levels, or Settings › Access levels). A person's Access section assigns an Account level. Project Members assigns a Project level. Team membership assigns a Team level. These assignment controls do not create another copy of the level.
The Account level, group by group
The Account level reads from top to bottom. Each switch is Hidden, View or Edit, or only Hidden or Edit where View has no meaning.
| Group | Switches | What they do |
|---|---|---|
| Finances & rates | Revenue, Billable rates, Cost rates, Practice finances, and Entity financial access | Revenue is what the practice earns. When Revenue is Hidden, Quotes and Invoices are Hidden too. Billable rates and Cost rates are separate: one does not need the other. Practice finances covers salaries, overheads and labour cost. Entity financial access sets which entities' finances they see. |
| Projects | Projects and Default project access | Everyone sees projects. Projects Edit lets a person create projects and set rate rules. It never lets them change other people's time. Default project access sets the Project level they get on projects they are not added to by name. |
| Team | Staff & team management | Edit manages staff, practice Roles, teams and access assignments. |
| Reports | Practice reports | Edit changes the built-in reports and who they are shared with, the default reports, the reports placed on pages, custom columns, "Add to all invoices" and report PDF uploads. |
| Records | Clients & Contacts, Quotes | View reads them. Edit creates and changes them. |
| Invoices | Invoices, Approve invoices, Send invoices, Mark milestones billed outside Monument | Invoices View reads invoices and their payments. Edit creates and changes them. Approve invoices also returns an invoice to draft and voids it. Mark milestones billed outside Monument marks a billing milestone that was invoiced before Monument as billed, and removes the mark. Approve, Send and Mark milestones billed outside Monument need Invoices Edit. |
| Expenses | Expense claims, Approve expense claims, Mark claims paid | Expense claims covers staff claims, supplier invoices and direct costs. A person with Approve expense claims can approve their own claims. Approve and Mark claims paid need Expense claims Edit. |
| Time | Override timesheet locks, Mark time non-billable | Override timesheet locks lets them change a locked entry. Each change is recorded. Mark time non-billable lets them choose whether an entry is billable. |
| Admin | Project templates, Invoice templates, Accounting integrations, Practice settings, Activity log, API, Billing (subscription) | Each switch opens one admin job. Activity log View reads the practice's activity. Activity log Edit also undoes changes. |
Some things have no switch, because everyone has them:
- Everyone records their own time, leave and admin time.
- Everyone sees leave and public holidays.
- Everyone sees the Project schedule and the Resourcing schedule. The people on the Resourcing schedule, and their details, follow the person's Team levels.
- Everyone can create, change and run their own reports.
- Everyone keeps their personal settings.
A switch that another switch caps stays on the screen, greyed out, with the reason under its name. For example, with Revenue Hidden the Invoices row shows "Capped by Revenue". The value you saved returns when you raise the switch that caps it.
The Organisation & Finances page
The page opens when a person can see any part of it. Each part has its own rule:
- Financial forecast and its scenarios: Revenue View or Edit, and View on project revenue on at least one project or on Invoices.
- Salaries and overheads: Practice finances.
- Cost-rate figures: Cost rates.
Settings tabs
A settings tab needs Practice settings Edit. An area tab also needs its area's switch. An area switch never opens settings on its own.
| Settings tab | What it needs |
|---|---|
| Practice details, Entities, Data Import, Tags, Leave, Expenses | Practice settings Edit. Purchase order numbering on Expenses also needs Quotes Edit. |
| Time, Team members | Practice settings Edit and Staff & team management Edit |
| Invoices & accounting | Practice settings Edit and Invoices. With Invoices View the tab is read-only. Fee proposal numbering also needs Quotes Edit. Accounting integrations Edit opens the accounting connection on its own. |
| Finances | Practice settings Edit and Practice finances. View is read-only. |
| Contacts | Practice settings Edit and Clients & Contacts |
| Projects | Practice settings Edit and Projects. With Projects View the tab is read-only. |
| API | API Edit |
| Billing | Billing (subscription) Edit |
| Activity | Activity log View or Edit |
Practice settings also covers logos, custom holidays, leave entitlements, tax and account codes, invoice description templates and notification settings.
Account access follows the person
Monument finds a person's Account level in this order:
- An access level chosen for that person.
- The default on their practice Role, such as Architect.
- The firm's default Account level.
An explicit choice stays with the person if their practice Role changes. An inherited choice follows the Role or firm default. The picker shows real access levels; the resolved level and its source tell you which rule supplied it. A practice Role alone does not open a project.
The built-in Director level has every switch at its highest value. Office administrator manages invoices, quotes, expenses, staff and teams, contacts and timesheet corrections. It has no rates and cannot create projects. Project owner runs the projects they own and reads everything else. Team member records their own time and expenses. A custom level may combine any switches, but it does not become a Director. Only a Director can change Account assignments, act as someone else, or manage the subscription.
Default project access has two kinds of value:
- A Project level, such as Viewer. The person gets that level on every project they are not added to by name.
- None. The person sees only the projects they have been added to or are allocated to.
Check the effective project result before you assume they will see its Revenue and Expenses.
Project access has a source and a limit
Project access can come from a manual Members grant, project ownership, a matching people rule, an allocation, or Default project access. The source matters. A manual grant and ownership are deliberate decisions, so they keep their full values. The other sources are automatic. Automatic grants are limited by the person's Account Practice finances for Revenue and Expenses, and by their Account Revenue for Revenue. A person with Practice finances Hidden may have a Project level that says Revenue View but still get Revenue Hidden from an allocation.
Changing a project's tasks, people and time follows the Project level only. No Account switch gives this on every project.
Milestones is Hidden, View or Edit on each Project level. View shows the project's milestones. Edit adds, renames, re-dates and deletes them, and sets their type, lock, status, task targets and links. Hidden hides the project's milestones from that person. Tasks Edit does not change milestones. Every level started at its Tasks value: Edit with Tasks Edit, View otherwise, and Edit where it already changed milestone billing.
Milestones does not depend on financial access. No Revenue or Account switch turns it off. The amounts on a milestone follow Revenue on the same project. Revenue View shows a billing milestone's amount, claim and invoice figures. Changing those amounts, the draft invoice or the project's billing schedule, or making a milestone a billing milestone, needs Milestones Edit and Revenue Edit together. A person with Milestones Edit and no Revenue sees billing milestones with their names and dates, and no financial figures.
Contacts is Hidden, View or Edit on each Project level. It works together with the Account Clients & Contacts switch: a person needs both. View on both shows the project's Contacts tab, with each contact's email and phone. Edit on both adds contacts to the project and removes them. Changing the project's billing contact needs Contacts Edit on the project; Tasks Edit does not change it. Owner, Manager and Finance started at Edit; every other level started at View. Confidential projects hide their contacts like everything else on them.
Budget usage on a project follows the Project level's Budget usage switch. Budget usage figures that cover the whole practice follow Account Practice finances View.
The Project access-level table marks the Project owner default and Project lead default. Project ownership uses the Revenue and Expenses values in the Project owner default directly. There is no second ownership-finance switch. A Project lead gets the Project lead default when their team is assigned. Manual Project grants remain separate.
Project grants can apply to one task branch instead of the whole project. Confidential projects and entity financial access can limit the result further. Project Viewer gives View for Tasks, Resources, and Time and hides Revenue and Expenses. A person can still record their own time where their task rules permit it.
Team access and personal work
Team levels control access to other people in the team. Lead, Member, and Viewer levels separate profiles, time, time approval, leave, leave approval, and schedule. A person's own time and leave are also subject to their task visibility and workflow rules. A Team level does not itself give Project Revenue or Practice finances. The Team table marks the Team member default used when a team membership has no explicit level.
Deleting an access level requires a replacement. Existing people, assignments, and defaults using the deleted level move to that replacement. The protected Director Account level cannot be deleted because the firm must keep a Director.
Reports and entity financial access
An access level has no list of reports. Who can run a saved report is set on the report itself. A report is shared with any mix of these:
- everyone;
- a job role;
- a team;
- people by name;
- an Account access level.
A report also has an except list. A person on that list cannot run the report, whatever its sharing says. The person who created a report can always run it, unless they are on its except list.
Sharing never shows more data than the person's own access allows. The report's data must still be reachable through their Account, Project, Team, branch, and entity access. Rows and columns they cannot see stay hidden. Administrators can run every report whose data is switched on for the practice.
New practices start with My time, Hours against budget and the tabs on each list page (such as Active Projects and Draft Invoices) shared with everyone. Each person still sees only the rows their access allows. Every other built-in report is shared with the Director, Office administrator and Project owner levels. To change the built-in reports, or who they are shared with, a person needs Practice reports Edit. A person's own reports need no switch.
A person's Report access tab lists every report and says why they can or cannot run it. From there, or from a report's Who can run this report list, you can share a report with one person or switch it off for them. Switching it off puts them on the report's except list.
Entity financial access is another limit. An Account level may cover all entities or a selected set. A person may also have their own entity limit. The effective range is the entities allowed by both. Selecting no entities hides financial data on purpose.
A worked example
At Northlight Architects, Sarah Chen has the Team member Account level from her Architect practice Role. Team member's Default project access is Viewer, so she can read Riverside Civic Library's tasks and record her own time where allowed. Viewer hides Revenue and Expenses. If a Director gives her a Project level with Revenue View on that project, an allocation alone may still leave Revenue Hidden while her Account Practice finances is Hidden. A manual Project grant keeps its full values. Preview Sarah's effective access on the project to check the real result.
Sarah can run My time and Hours against budget and open every list-page tab, because they are shared with everyone. She cannot run the other built-in practice reports, because they are shared with the Director, Office administrator and Project owner levels. To let her run one, share it with her by name from her Report access tab. She still sees only the figures her own access allows.
Use a person's permission preview to check ownership, manual grants, task branches, and entity limits. Preview is read-only. Act-as is a separate mode.
When a result looks wrong
- A level says Revenue View, but the person sees no financial figures. Check whether the Project grant came from an allocation or Default project access, then check Account Revenue, Practice finances and entity financial access.
- A saved report is missing. Check who the report is shared with, its except list, and the person's access to its data.
- A Role change did not change someone's Account level. Check for an explicit Account choice.
- A project is missing. Check its assignment or people rule, task branch, and confidential status, and the level's Default project access.
- A settings tab is missing. Check Practice settings and the tab's area switch.
Project attention limits are on Settings → Projects, the utilisation assumption on Settings → Finances, and expense approval on Settings → Expenses. Access levels and their defaults live on the Access levels page. Continue with staff permissions and project access for the assignment workflows.
Search Monument help
Search help articles and open a result.