Permissions give you complete control over what people can do with the things you've shared with them!

Members and guests will get permissions based on the item and its location.

In the event that someone has conflicting permissions in ClickUp, then the most specific and highest permission will be honored.

  • Task level permissions override List level permissions, which override Folder, and Space level permissions

  • Permissions set for a specific person override Team permissions

  • Create & Edit (full) permissions override can edit permissions, which override can comment, which override can view

Practical examples

Here are some practical examples to demonstrate how this works:

Scenario: Sam is a member of two teams. Team A has can view (read-only) to a Folder and Team B has can edit permissions to the Folder

Result: Sam will get the highest permission, so they can edit.


Scenario: Alex is a member of a team but also has specific permissions to an item. They are a member of Team A. Team A has can edit permission to task 1. Task 1 is shared with Alex to give them can view permissions.

Result: The more specific permission wins, so Alex has can view permissions to task .


Scenario: Jordan has can view permissions to task 1. Jordan's team, Team A, has can edit permissions to the List where task 1 lives.

Result: The most specific permission wins. So Jordan can view task 1, and can edit all other tasks within the List.


Scenario: Charlie is a member of Team A. Team A has can view permissions to List 1. Using the new sharing modal, you can expand a Team and see each individual Team member and customize their individual permissions. Charlie is given can edit permissions to List 1.

Result: List 1 is automagically shared with Charlie, separate to Team A, and they are granted can edit permissions which are more specific, and override any Team permissions.


Scenario: Jamie is a member of Team B. Team B has create and edit (full) permissions to List 1. As in the above scenario, Jamie is given can view permissions to List 1 from within their Team.

Result: List 1 is automagically shared with Jamie, separate to Team B. The more specific permission wins, so Jamie can view List 1.


Scenario: Stevie has can view permissions to tasks in List 1. Task A's home list is List 1. Task A is also added to List 2 using our Tasks in Multiple Lists feature. Stevie has create and edit (full) permissions to List 2.

Result: The highest permission wins (regardless of whether it is from the home List or secondary List), so Stevie has create and edit (full) permissions to Task A.


Scenario: A Doc is shared with a private task, and appears as an attachment on the task. Everyone, including guests, who have access to the task can also access the Doc. The task is shared with a guest with can comment permissions.

Result: The Doc will inherit permissions from the task where it is attached, so the guest has can comment permissions to the Doc.


Scenario: A Doc is shared with a private Folder. This creates a Doc view at the Folder level. Everyone, including guests, who have access to the Folder can see the Doc view. The Folder is shared with a guest with can view permissions.

Result: The Doc view will inherit permissions from the location where it is shared, so the guest will have can view permissions.


Scenario: A private task is shared with Jessie, a Workspace member, who is given can comment permissions on the task. Jessie then shares the task Carey, a guest, and grants them can comment permissions.

Result: Jessie can only provide Carey with can comment or can view permissions to the task.

Workspace members who have access to an item will be able to share that item with others, including guests, and give them the same or less permissions.


Want to learn more?

Did this answer your question?