ClickUp guest access: review shared locations and inherited subtasks

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Review the actual role and object

ClickUp documents different access behavior for members, limited members and guests. Guests do not receive location access by default; particular locations or tasks must be shared under the applicable role rules. Its permissions guide says subtasks inherit the primary parent task's permissions.

The privacy guide also states that guests cannot access Spaces. Our recommendation is to list the exact resources and required capabilities instead of treating guest as a complete access specification.

A fictional delivery review

Assume a client reviewer needs an approved delivery task and its review subtasks, but not internal negotiation notes. A project owner proposes sharing a whole delivery List because it is convenient. Before approving that scope, inspect every representative resource the List would expose.

This example is a planning exercise. It sends no invitation, changes no permissions and does not describe an actual client account.

Write a visibility matrix

• Approved delivery: visible with the intended review capability.
• Review subtask: inherits the intended parent scope and is usable.
• Internal negotiation: follows its separately approved audience.
• Related task: available only through an appropriate permission path.
• Custom Field: sensitivity and effective visibility reviewed.
• External document: its own access checked independently.

Inspect the effective path

1. Identify the intended collaborator role and current plan controls.
2. List each required task, subtask and supporting resource.
3. Review the sharing of the enclosing location and individual task.
4. Check inherited subtask permissions against the matrix.
5. Use an authorized representative account for synthetic access checks where possible.
6. Inspect required actions such as reading or commenting separately from visibility.
7. Record the approved scope and who reviews later changes.

Keep scope proportional

Our access-design advice is to avoid sharing an entire work container solely to make one linked item convenient. Determine whether the reader needs that broader context. Conversely, sharing only a landing task may be insufficient when the actual review depends on another protected document.

Keep a small register of what was shared and why. When the engagement ends, review direct shares, location membership and supporting documents under the organization's approved process.

Acceptance criteria

Approve the design when required work is accessible under the intended role, internal material follows its approved scope and supporting resources have been checked. A hidden column or a filtered view is not sufficient evidence of access restriction. This source-based checklist is not a live permission test or security certification; actual account controls and organizational policy determine the final sharing decision.