The Gantt, Kanban, and Task List components behave the same way no matter which access pattern is using them - Internal Salesforce, Contractor Workspace, Partner Workspace, Customer Workspace, or a page built for Guest access. What each user sees is governed entirely by their Field-Level Security (FLS) and permission set configuration, not by which pattern they're on. This article covers that shared mechanism once, so it doesn't need repeating separately for every pattern.

The Baseline Permission Set

For external, Experience Cloud-based access (Contractor, Partner, or Customer Workspace), Precursive ships an out-of-the-box permission set, Precursive Customer Workspace Minimum Access, granting read-only access to the Contributor, List, Participant, Task, and Task Dependency objects. This is enough for Gantt, Kanban, and Task List to load and show core functionality: task hierarchy, dates, completion status, dependencies, list ordering, and Participant names. Internal Salesforce users typically have broader access already through their standard permission sets and don't need this one.

All three components are built to degrade gracefully rather than fail to load when a user lacks access to a particular field - each renders what it can and hides only the elements that depend on inaccessible fields, regardless of which access pattern the user is on.

Features That Need Additional Access

The baseline permission set intentionally does not include everything - some visual detail requires additional field or object access on top of it, for any user missing that access, internal or external.

To show...	You need to additionally grant...
Planned/remaining/actual hours on the Task card and its tooltip	Read access to the hours fields on Project Task
Task Category colour on the card	Read access to the Task Category object and its colour field - requires its own additional permission set, not included in the baseline
Contributor avatars (photos, not initials)	Read access to the Resource and User photo fields. Without it, avatars fall back to initials for any user with restricted access
Drag / resize / reorder on the Gantt or Scheduler	Edit access to Start Date, End Date, and Duration on Project Task
Editing Predecessor/Successor dependencies	Create/Update/Delete access on Task Dependency - without it, dependencies display read-only
List sort by custom order	Read access to the Order field on List - without it, lists fall back to alphabetical sorting
The Milestone Timeline component	Access to the Apex class that powers it, plus the Milestone-related sharing fields - not included in the baseline by design. Without this access, users see a clear access message rather than a broken component

Where access is missing, the related icon, column, or detail is hidden or falls back to a simpler default - the rest of the component continues to work normally, for every access pattern.

Contact-Based Participants

Any Workspace can include a Salesforce Contact added directly as a Participant, without a linked Resource record - see "Customer Contacts as Participants" for how this works.

Displaying a Contact-based Participant fully depends on three additional fields on the Participant object: Contact, Participant Type, and Participant Classification. None of these are included in the baseline permission set, and no other Customer Workspace permission set grants them either. If you need Contact-based Participants to display fully, grant read access to these three fields yourself as an additional step - this is a known gap, not a configuration you are expected to already have.

Related Resources

• Precursive Access Patterns: Choosing How to Work With Others
• Customer Contacts as Participants