Browse articles

What each access switch controls

A reference to the Account access level's other switches: contacts, project creation, expense claims, practice reports and staff management, and where project control lives now.

What you'll achieve

Find the one switch that gives or holds back a job, without changing anything else.

You'll end up with: You know which switch does each job, and which jobs no Account switch controls.

Most practices never need this page. The built-in levels, Director, Office administrator, Project owner and Team member, fit most people, and the steps before this one cover the switches that matter most: practice finances, rates, project access and team access. Come here when one person needs one job added or taken away.

Every switch below sits on an Account access level, in Team, then Access levels. Change a level and everyone who holds it changes with it. To check the result, preview a colleague's view as described in Choose each person's access level.

The switches at a glance

SwitchGroupSettingsWhat Edit addsBuilt-in levels with Edit, as a new practice starts
Clients & ContactsRecordsHidden, View, EditCreating and changing contacts and contact typesDirector, Office administrator, Project owner (Team member has View)
ProjectsProjectsView, EditCreating new projects and setting rate rulesDirector
Expense claimsExpensesHidden, View, EditSubmitting and changing claims, supplier invoices and direct costsAll four
Approve expense claimsExpensesHidden, EditApproving or returning claims when approval is requiredAll four
Mark claims paidExpensesHidden, EditMarking claims paidDirector, Office administrator
Practice reportsReportsHidden, EditChanging the practice's built-in reports and who they are shared withDirector
Staff & team managementTeamHidden, EditCreating people and teams and editing their detailsDirector, Office administrator

The rest of this page explains what each one does and does not do.

Clients & Contacts

Hidden removes the Contacts area. View opens the shared directory without create or edit actions. Edit allows changes to contacts and contact types.

Linking a contact to a project needs two things together: Contacts Edit, and Tasks Edit on that project. Contacts Edit alone can't change a project the person can't edit. Full guide: Contacts access.

Projects

Everyone has at least View, so everyone sees the projects their project access lets them see. Edit adds only two jobs: creating new projects and setting rate rules. It gives no power over existing projects. A person who creates a project becomes its Owner, but only on that project. Full guide: Project creation access.

Expense claims, Approve expense claims and Mark claims paid

Expense claims covers staff claims, supplier invoices and direct costs, including those with no project. Hidden removes the area, View allows reading, and Edit adds submitting and changing.

Approve expense claims and Mark claims paid both need Expense claims Edit. With Expense claims at View or Hidden, the two rows stay on screen, greyed out, with the reason under their names. A person who can approve claims can approve their own.

This is different from Expenses on a project access level, which controls who sees a project's costs. Full guide: Expense claims access.

Practice reports

Everyone can create, change and run their own reports, and run any report shared with them. There is no switch for that. Who can run a saved report is set on the report itself, and sharing never shows a person data their other access hides.

Practice reports Edit lets a person look after the practice's reports: change the built-in reports and who they are shared with, choose the default reports, place reports on pages, add custom columns, use "Add to all invoices", and upload report PDFs. Full guide: Report access.

Staff & team management

Edit covers creating people and teams and editing their details. It does not cover creating or changing access levels, assigning Account levels, or entity financial access. Those stay with the Director.

Who can give project and team access levels follows those levels, not this switch. Full guide: Staff management access.

Jobs no Account switch controls

Changing an existing project's tasks, people and time comes from the Project access level a person holds on that project, not from an Account switch. Until October 2026 there was a Project administration switch; its jobs moved to project access levels and a few other switches. Project admin access lists where each job went, and Give someone access to one project shows how to give it.

Troubleshooting

  • A person still can't do the job after you changed a switch. Check you changed the level they actually hold, and that the job isn't one that comes from project or team access instead.
  • Approve expense claims is greyed out. Raise Expense claims to Edit first.
  • Someone can create projects but not change an existing one. That's expected. Give them a project access level on that project.
  • A shared report shows someone fewer rows than you see. Sharing never opens data. They see only what their own access allows.

Where this fits next

Last in Bring your team in with the right access: secure accounts with two-factor sign-in, sessions and API keys.

Search Monument help

Search help articles and open a result.