Team & Region-Based Sharing

Highlights

Team & Region-Based Sharing Automatically share Projects, Phases, and Resources with your Teams and Regions - no more manual sharing rules needed for group-level access control. Learn more about Teams and Regions.

What Changed

Teams and Regions now 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

• 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.)
  NOTE: only when Internal Sharing Model for these objects is set to Private.
• Reassign or remove Team/Region assignments — access updates automatically
• If a Team/Region has a Parent, the Parent group also receives the same access

Enablement Guidance

Sharing via Teams and Regions is applicable only when Internal Sharing Model for Precursive objects (Projects, Phases, Resources, Project Tasks, Budgets, Milestones, etc.) is set to Private

• Post-install creates User Groups for all existing Teams and Regions automatically
• Review existing Team and Region assignments to ensure access is configured as expected after upgrade
• Note: Supervisor access continues to work through Project Access Level (PAL) — Team/Region-based read access does not automatically extend to supervisors

Contextual Booking & Timesheet Recalculations

Highlights

Contextual Booking & Timesheet Recalculations Booking and Timesheet recalculations now process only affected Participants instead of entire Phases, improving performance on large Projects.

What Changed

The system now recalculates Bookings and Timesheet Entries only for Participants directly affected by Task or Contributor changes, rather than recalculating every Participant within the entire Phase. A new background job queue manages these recalculations asynchronously.

Enablement Guidance

No manual steps necessary.

Magic Assign Performance for Large Resource Pools

Highlights

Magic Assign now handles organisations with more than 100 Resources matching a filter criteria without hitting CPU limits - no more timeout errors when finding the right person for the job. Learn more about Magic Assign.

What Changed

Magic Assign now processes Resources in parallel chunks to avoid Salesforce CPU Time Limits when loading large numbers of matching Resources. Previously, organisations with even 50+ Resources matching a single Role would hit timeout errors.

How It Works

• Expect longer loading times for very large Resource pools (100+ Resources), but the process will complete without errors
• The loading overlay indicates processing is in progress - wait for it to complete before interacting with results

Enablement Guidance

No manual steps necessary.

Data Model

No changes in the Data Model in 2.17 release.

Review all Release Notes.