Teams and Regions offer a modern, scalable way to organize delivery operations in Precursive. They replace legacy fields (Department and Location) with a consistent structure used across Resources, Projects, Phases, Time Off, the Resource Plan, and reporting.
By assigning every Resource to a Team and a Region — even if your organization operates within a single geographic area — you ensure consistent planning, accurate Time Off behavior, and clear reporting across your Professional Services operations.
What Are Teams?
A Team represents a functional group within your organization.
Examples may include: Implementation, Customer Success, Managed Services, or PS Delivery.
Teams help you:
-
Group Resources into meaningful delivery units.
-
Filter and group work in the Resource Plan by delivery team.
-
Report on performance, utilization, and delivery metrics by team.
-
Track which team is responsible for a Project or Phase.
Teams are a flat structure with no hierarchy.
What Are Regions?
A Region represents a geographic delivery area such as EMEA, North America, or APAC.
Regions help you:
-
Apply Time Off rules based on geography.
-
Plan work using Region-based availability.
-
Segment Projects and Phases by delivery area.
-
Run Region-specific portfolio and utilization reporting.
Regions support up to a five-level hierarchy, for example:
- Global
- Apac
- EMEA
- DACH
- Austria
- Germany
- Switzerland
- Spain
- United Kingdom
Hierarchy cannot exceed five levels, and circular references are not allowed.
Where Teams and Regions Appear in Precursive
Assign Teams and Regions to Resources
Each Resource record includes two fields:
You can update these fields at any time on the Resource record.
These fields determine how a Resource is grouped in planning, how Time Off is applied, and how Resource-related data is segmented in reporting.
Assign Projects and Phases to Teams and Regions
Project.Team, Project.Region, Phase.Team, and Phase.Region fields allow for consistent segmentation, ownership assignment, and reporting across all levels of delivery.
Project
Projects now include:
-
Project.Team
-
Project.Region
These fields help you identify which Team and Region own or deliver each Project.
Phase
Phases include:
These enable granular portfolio segmentation and Phase-level ownership.
Filter by Teams and Region on the Resource Plan
The Resource Plan now supports:
Using these options, you can focus on specific delivery groups or regional availability when allocating work.
These replace the previous Department and Location options. In case your organization used these in the previous versions, review section Moving from Department and Location to Teams and Regions below that explains how the transition process is done.
Team & Region-Based Sharing
Teams and Regions automatically manage data access through Salesforce User Groups. When you assign a Project, Phase, or Resource to a Team or Region, all members of that group receive read-only access to the relevant records and their related objects. Parent Teams/Regions inherit visibility from their children, creating a natural hierarchy of access without manual configuration.
How it works?
NOTE: only when Internal Sharing Model for Project, Phase, or Resource is set to Private.
- Create a Team or Region record — Precursive automatically creates a corresponding User Group
- Assign Resources to Teams/Regions — their Users are automatically added to the relevant User Group
- Assign Projects, Phases, or Resources to Teams/Regions — all group members receive read-only access to those records and related objects (Project Tasks, Budgets, Milestones, etc.)
- Reassign or remove Team/Region assignments — access updates automatically
- If a Team/Region has a Parent, the Parent group also receives the same access
Time Offs Per Regions
Time Off entries now require a Region. This ensures that Time Off behaves consistently with the Resource’s assigned Region and its hierarchy so that regional calendars and rules remain consistent.
NOTE: If your organization does not require regional segmentation, all Resources should be assigned to a single default Region, such as Global.
Time Off records should also reference this same default Region to ensure consistent scheduling behavior.
Assigning a Region is recommended for every Resource so that planning, Time Off, and reporting behave predictably.
Reporting With Teams and Regions
All standard Precursive utilization and delivery reports now use Team and Region fields.
Reports that previously grouped by Department or Location have been updated accordingly.
If you use custom reports, review and update them to reference the new fields.
Moving from Department and Location to Teams and Regions
If your organization upgraded from a previous version that used Department and Location, Precursive performed a migration to align your org with the new model.
The migration includes:
-
Creating Team records from existing Department values.
-
Creating Region records from existing Location values.
-
Updating Resources to use new Team and Region lookups.
-
Updating Time Off to reference Region instead of Location.
-
Updating Projects and Phases with new Team and Region fields.
-
Updating Resource Plan filtering and grouping to use the new fields.
-
Updating standard reports, report types, and dashboards.
About the default Region
If Resources or Time Off previously had no Location assigned, a default Region (for example, Global) may have been automatically created and assigned during migration to preserve existing scheduling behavior.
For ongoing usage, customers may rename, reorganize, or replace this Region depending on their operational model.
Administrators can verify migration status under:
