Partner Workspace

Highlights

Partner Workspace is a secure portal enabling external partners-such as systems integrators, contractors, and consultants-to manage projects they are delivering with you. Partner Workspace centralizes key delivery components including, Project plans, Milestones, Tasks, Health Status, Timesheets, and expenses to ensure smooth collaboration between internal teams and external delivery partners. Learn more here about Partner Workspace, or contact customersuccess@precursive.com.

What Changed

Partner Workspace provides external delivery partners with controlled access to the Projects and Phases they are assigned to. Partners can view and update Project Tasks, log time against Timesheets, submit Expenses, and collaborate on delivery activities.

Partner License Type

A new license type has been introduced to track Partner users separately from internal users. Partners are identified automatically when a Resource record has both a Contact and User linked, the User Type is not Standard, and the User is Active. Partner license usage is now visible in Precursive HQ alongside other license types and included in license management reports.

User Settings Migration to Project Access Levels

To support the Private Sharing Model and Partner Workspace, legacy Precursive User Settings have been replaced with Project Access Levels. This provides more granular, per-Participant control over what actions users can perform on Projects, Phases, and related records.

The following User Settings have been mapped to Project Access Levels:

• Can see timesheets as Admin
• Can submit expenses to all projects
• Can change all projects' data
• Can book other people to projects

Learn more about upgrading to Project Access Levels here.

How It Works

Partner Workspace Access

1. Create a Resource record linked to both a Contact and a Partner Community User
2. Add the Resource as a Participant to the relevant Phase(s)
3. Assign an appropriate Project Access Level to control what the Partner can view and edit
4. The Partner logs into the Partner Community and sees only the Phases they are assigned to

Project Access Levels

Project Access Levels define what each Participant can do within a Project. During upgrade, the system automatically:

1. Creates default Project Access Levels based on common permission combinations
2. Maps existing User Settings to new Project Access Level records
3. Assigns the appropriate Project Access Level to existing Participants based on their User Settings

After upgrade, administrators can create custom Project Access Levels to match their organization's access requirements and assign them to Participants individually or by Role.

Enablement Guidance

Post-Install Action Required:

Navigate to Precursive HQ > Critical Updates and verify the following tile: Map User Settings into Project Access Levels on Participants.

This Critical Update:

• Creates default Project Access Levels based on predefined permission combinations
• Maps deprecated User Settings to new Project Access Level records
• Assigns Project Access Levels to existing Participants

Recommended Configuration:

• Review the default Project Access Levels created during post-install and customize as needed
• Create Role-based default Project Access Levels for consistent assignment to new Participants
• For Partner users, we recommend using Individual Contributor Permission Sets

Project Health Ratings Simplification

Highlights

To simplify Health Ratings, we are deprecating the "Apply to Entire Project" feature. Health Ratings will now be applied directly at the Phase level.

What Changed

The "Apply to Entire Project" option on Health Ratings has been deprecated. Previously, this feature allowed users to create a single Health Rating that would apply across all Phases in a Project, but the implementation required selecting both a Project and a Phase, which caused confusion.

Going forward, Health Ratings are created directly at the Phase level. The Project-level Health Rating display now aggregates the latest Health Rating from all associated Phases, providing a consolidated view without the ambiguity of the previous approach.

How It Works

Creating Health Ratings

1. Navigate to the Phase record
2. Go to the Health & Insights tab
3. Click "New" on the Health Rating History related list
4. The Project and Phase fields are automatically populated
5. Complete the Health Rating details and save

Viewing Health Ratings

On the Phase:

• The Health & Insights tab displays the latest Health Rating for that Phase
• The Health Rating History related list shows all historical Health Ratings

On the Project:

• The Health Rating icon in the header displays the most recent Health Rating from any associated Phase
• The Health & Insights tab shows all Health Ratings across all Phases
• The Health Rating History related list includes the Phase column to identify which Phase each rating belongs to

For Single-Phase Projects, the behavior remains unchanged as the Phase and Project Health Ratings are effectively the same.

Enablement Guidance

Layout Updates Recommended:

With the "Apply to Entire Project" feature deprecated, we recommend reviewing your layouts:

• Remove the "Apply to Entire Project" field from Health Rating page layouts
• Remove the "Apply to Entire Project" field from Health Rating header (if displayed)
• Review Health Rating related lists on Project and Phase layouts to ensure appropriate columns are displayed
• The Health Rating related list on Phase now uses a Dynamic Related List component with enhanced columns

No Data Migration Required:

Existing Health Ratings created with "Apply to Entire Project" = TRUE will continue to function. The deprecation only affects new Health Rating creation.

Enhanced Task Template Support

Highlights

Improved handling of large and complex Task Templates, now supporting up to 500 Tasks.

What Changed

Significant improvements have been made to Template import processing to support larger and more complex Templates. Previously, importing Templates with more than 200 Project Tasks could result in Tasks not being scheduled according to their dependencies, or scheduling failures when modifying predecessor dates.

The scheduling engine has been optimized to handle Templates with up to 500 Project Tasks while correctly applying all dependencies and Lead/Lag values during import.

Enablement Guidance

No configuration changes required. The improvements apply automatically to all Template imports after upgrading to version 2.11.

Subtask and Parent Task Sharing

Highlights

Updated customer sharing rules to ensure sub-tasks can only be shared if their Parent Task is also shared. This prevents inconsistencies when granting customers access to tasks.

What Changed

The logic for sharing Project Tasks with external users (Customer Workspace) has been updated to respect the Task hierarchy. Previously, if a subtask was marked as "Shared with Customer" but its Parent Task was not shared, the Kanban and Gantt views in Customer Workspace would fail to load, affecting all shared Tasks.

The sharing calculation now considers the full Task structure. A subtask can only be shared externally if all of its ancestor Tasks (Parent, Parent's Parent, etc.) are also shared. When a Parent Task's sharing status changes, all subordinate Tasks have their sharing flags recalculated automatically.

How It Works

Sharing Behavior:

• When you share a Parent Task with customers, its subtasks can also be individually shared
• When you unshare a Parent Task, all its subtasks are automatically unshared (regardless of their individual "Shared with Customer" setting)
• The "Available in Customer Workspace" and "External Sharing" flags on Project Tasks now reflect the effective sharing status based on the full hierarchy

Customer Workspace Experience:

• Customers only see Tasks where both the Task and all its ancestors are shared
• Kanban and Gantt views load correctly even if some Task structures have inconsistent sharing settings
• Tasks remain visible in the Tasks component and Tasks related list based on the corrected sharing logic

Enablement Guidance

Post-Install Action Required:

Navigate to Precursive HQ > Critical Updates and verify the following tile: Recalculate Task Sharing Logic Based on Task structure.

This Critical Update runs the process to recalculate sharing flags across all Project Task records, applying the new hierarchy-based logic to existing data.

Review Existing Sharing:

After the Critical Update completes, review any Project Task structures where subtasks were previously shared but Parent Tasks were not. These subtasks will no longer be visible in Customer Workspace until their Parent Tasks are also shared.

Data Model

Deprecated field

Object: Health Rating

• Apply to Entire Project (preempt__applyToEntireProject__c)

Review all Release Notes.