Setting Up Roles and Permissions

Overview

Monument's built-in roles work well for most teams, but you can create custom roles with specific permission combinations to match your organisation's structure. This guide covers creating and managing roles across all three permission domains.

Creating an Organisation Role

1. Navigate to Settings > Roles & Permissions.
2. In the Organisation Roles section, click Add Role.
3. Enter a role name (e.g. "Finance Manager", "HR Admin").
4. Toggle individual permissions on or off:
   • Projects — view all, edit, create, delete
   • Resources — view, manage, view salaries
   • Invoicing — view, create, approve, send
   • Reports — view, create, share
   • Settings — view, edit company settings
   • Financial — view costs, view revenue, view profit
5. Click Save.

Creating a Project Role

1. In Settings > Roles & Permissions, go to the Project Roles section.
2. Click Add Role.
3. Enter a role name (e.g. "External Consultant", "Observer").
4. Toggle project-level permissions:
   • Tasks — view, create, edit, delete
   • Financials — view revenue, view costs, edit financial items
   • Milestones — view, create, edit
   • Team — view project team, manage members
   • Invoices — view, create project invoices
5. Click Save.

Creating a Pool Role

1. In Settings > Roles & Permissions, go to the Pool Roles section.
2. Click Add Role.
3. Enter a role name and toggle pool-level permissions.
4. Click Save.

Assigning Roles to Users

Organisation Role

Organisation roles are assigned when inviting a user or from their resource profile:

1. Go to Resources and open a team member's profile.
2. In the Access section, select their Organisation Role from the dropdown.
3. Click Save.

Project Role

Project roles are assigned per project:

1. Open a project and go to the Team tab.
2. Click Add Member or click an existing member's role.
3. Select the appropriate Project Role.
4. Click Save.

Pool Role

Pool roles are assigned when adding members to a pool:

1. Open a resource pool.
2. Find the member and click their role badge.
3. Select the new role.
4. Click Save.

Best Practices

• Principle of least privilege — give people only the access they need.
• Use organisation roles for broad access — things like "can view all projects" or "can manage settings".
• Use project roles for specific access — when someone needs elevated access on just one project.
• Review roles periodically — as team structure changes, roles may need updating.

What's Next

• Understanding the Permission System — how the three domains work together
• Permissions Reference — complete list of all available permissions
• Inviting Team Members — assign roles during onboarding