Understanding Resource Pools

What is a Resource Pool?

A resource pool is a group of team members that share a common characteristic — such as a department, skill set, or role. Pools serve two purposes in Monument:

1. Scheduling — allocate work to a pool when any member of the group could do it, rather than committing to a specific person.
2. Permissions — control access to projects and data based on pool membership.

Pool Membership Rules

Pools can include members in different ways:

Rule Type	How Members Are Determined
All	Every resource in the organisation
Role	All resources with a specific role
Department	All resources in a specific department
Skill	All resources with a specific skill
Explicit	Manually selected resources

When using rule-based membership (role, department, skill), new resources matching the criteria are automatically added to the pool.

Pool Allocations

When you create an allocation against a pool instead of a specific resource, you're saying "someone from this group will do this work." This is useful during early planning when you know you need a senior architect but haven't decided which one.

Pool allocations appear in a dedicated pool swim lane on the schedule. Later, you can convert them to specific resource allocations.

Pool Roles

Each pool member has a pool role that determines their permissions within the context of that pool:

• Pool Lead — can manage the pool, its members, and assign work
• Member — can view pool information and receive allocations

Tracks

Pools can have tracks — named sub-groups within the pool (e.g. "Interior", "Exterior", "Landscape"). Allocations can be assigned to a specific track, enabling more granular planning within a large pool.

What's Next

• Creating and Managing Resource Pools — set up and configure pools
• Resource Pool Permissions — control access through pools
• Understanding the Permission System — the full permission model