Browse articles

Set and preview a person's access

Save an account access level for a colleague, then preview Monument exactly as they see it.

What you'll achieve

Assign a person's account access level and verify its effect with truthful, read-only Preview.

You'll end up with: Priya Sharma has a saved Contributor access level that has been verified through Preview.

Start with the person, then verify the result

An account access level is the firm-wide part of a person's access. It controls eight capabilities: Business finances, Rates, Create projects, Project administration, Staff and team management, Expenses and claims, Reports, and Contacts. Project revenue and project expenses are separate. They come from project access levels, not directly from the account level.

This tutorial uses Priya Sharma and saves Contributor, the default account access level for new staff. Contributor can edit its own expense claim domain and view Reports, while Business finances, Rates, project creation, project administration, staff management, and Contacts stay Hidden. Its project visibility is Only assigned projects, so project rows still depend on an assignment or another valid grant.

Save the level before previewing

  1. 1

    Open Priya Sharma from Resources, then choose the Access tab.

  2. 2

    Click Edit, select Contributor from Account access level, and click Save Changes.

  3. 3

    Confirm Contributor is shown on the saved Access tab.

Saving matters because Preview resolves the selected person's real server-side assignment. It does not inspect an unsaved dropdown value.

This sequence explicitly covers selecting Contributor and clicking Save Changes before the preview begins.

Preview the saved principal

  1. 1

    Click Preview on Priya Sharma's Access tab.

  2. 2

    Check that Invoicing is hidden while Projects remains reachable.

    Step 2
  3. 3

    Click Stop Preview to return to your administrator view.

Reachability is not row access

Projects remains in the navigation for every active permission-bearing member. That does not mean Priya can see every project. With Only assigned projects, each visible row still needs a grant from an explicit assignment, ownership, a matching rule, or an allocation-derived default.

Troubleshooting

  • Preview does not match the dropdown. Save Changes first, then start Preview again.
  • A project is missing. Check the person's project grants, assignments, matching rules, and account project visibility. Being a staff member alone opens no project row.
  • You cannot change anything during Preview. This is expected. Stop Preview before editing.

Where this fits next

Continue with Business finances to see one account capability move from Hidden to View, or use the full permissions reference for all three permission domains.