Shareable 'private' views
under review
Mariana Irazu
Right now views are either private or public to everyone on a list/folder/space. It'd be great to have the possibility of sharing a specific view with a few people, but not everyone.
Log In
Michael Van Doorn
under review
Hey, everyone!
We're currently researching this feature for upcoming development and want to hear from you!
The current MVP is as follows:
- Private views are now shareable to users as well as teams.
- The list of users/teams available are only those of who have access to the hierarchy.
- Sharing to team will not share the hierarchy to users of the team who do not have access to the hierarchy.
- The owner of the view can determine who can / can't share the view at an individual level.
Let us know if that aligns with your request, if there's functionality you deem as 'critical' missing, or any feedback.
Thanks!
M
Maillard Sylvie
please do this !
S
Shreyansh Jain
Please do this. This is a must for my workflow
M
Michael Marriott
In agreement, great idea!
Melanie von Schorlemer
I fully agree. Private views should be sharable, e.g. with all team members that work with the same view.
Avraham Jay
just came here to say that perhaps there should be a way to limit views of a list (e.g. let's say users submit a list, I don't want them having access to the list that they submitted to as it contains other team members' info). Currently I need to set up an entire new list to achieve this, rather than simply share the view with the relevant person.
Lide
100% comparto la sugerencia.
S
Sasha Czerniawski
Would be great to restrict some views to certain people who may already have access to the rest of the list. ie. some users with permissions to access the list can see certain views that other users in the same hierarchy cannot
Tim Jasper
Yes. Specifically Private chats are critical. This would be a super feature (and obviously a no brainer).
Avraham Jay
Tim JasperI don't think that's what this post is about
Tim Jasper
Avraham Jay
Avraham Jay
Tim Jasperyep this is about something else, this is about making certain views within a list private :)
Tim Jasper
Avraham Jay I want to make a chat view in a list/folder/space private. Same.
Avraham Jay
Tim Jasper . ah, i see the connection :-) cool! Yes, some of this stuff seems so obvious to me/you/others...
K
Kelly Page
We want to share one list view with a specific person, they will not need to make changes. They will only need to view and click any of the links within the list. We would like to do this without either (1) making the specific person a guest or (2) without making the view public and available to anyone that has the link.
Michael Van Doorn
under review
Hey, everyone!
We're currently researching this feature for upcoming development and want to hear from you!
The current MVP is as follows:
- Private views are now shareable to users as well as teams.
- The list of users/teams available are only those of who have access to the hierarchy.
- Sharing to team will not share the hierarchy to users of the team who do not have access to the hierarchy.
- The owner of the view can determine who can / can't share the view at an individual level.
Let us know if that aligns with your request, if there's functionality you deem as 'critical' missing, or any feedback.
Thanks!
Mariana Irazu
Michael Van Doorn Hi MIcheal! Thank you so much for pushing this forward. Forgive my ignorance but can you clarify what you mean by 'hierarchy'? I imagine its about the hierarchy of having access to a list/folder, etc but I'm still not sure what "Sharing to team will not share the hierarchy to users of the team who do not have access to the hierarchy" means.
Aside from that the proposals look great!
Pierre Becher
Michael Van Doorn I think sharing of private views is a misleading description. Basically views should have the same permission controls like folders/lists/tasks, which means I can set a view to be private, or public, or share it only with specific people in the team (of course they need to have access to the hierarchy).
Tanner Wixom
Michael Van Doorn Thanks for looking into this feature. I'm not understanding the relationship between bullets 2 and 3; maybe I'm reading them wrong, but it seems like they contradict each other. If I have shared access to the hierarchy with Team A, every member of Team A will have access to the hierarchy. So why then does it matter that sharing to Team A will not share the hierarchy with Team A members who don't have access to the hierarchy? They already do have access because Team A shows up as an option to share with according to bullet 2.
Perhaps I'm misunderstanding what "hierarchy" means here.
Tim Jasper
Michael Van Doorn MVP? Basically what is requested globally (across views, subtasks, doc pages) is the ability to share these items with an individual user or team, without having to share the parent: space, task, doc etc.
Michael Van Doorn
Mariana Irazu: Happy to explain further!
If only a single user who is part of a Team has been given access to the hierarchy (Space/Folder/List) , we will show that Team under the sharing settings as an option and if you select to share to that team, it will only share to the single user (if other members of the team are given access to the hierarchy at a later point, they will see the view).
Let me know if you have any other questions!
Michael Van Doorn
Pierre Becher: Spot on! That's exactly what were aiming for.
View sharing options
- Public
- Private (just to you)
- Private (shared to anyone who has access to the Hierarchy where the view exists)
Michael Van Doorn
Tanner Wixom: Great Q! You're correct, in your example it would not matter since the Team has already been granted access to the hierarchy and therefore all members will see the view if shared.
To elaborate on these bullets; if a user who is part of "Team A" which consists of 3 members has been granted access to the hierarchy, we will show "Team A" under the view sharing settings. Selecting this Team will only make this view accessible to the single user and the other two users will not be shared the hierarchy (or view). Here's a video!
Michael Van Doorn
Hey, Tim Jasper! Those requests are similar yet different from the ask of sharing private views. We'd recommend leaving feedback on the threads associated
Thanks!
Mariana Irazu
Michael Van Doorn oh thats perfect! And while it wont affect my team right now, it definitely feels like the best functionality possible
Tim Jasper
Thanks Michael Van Doorn. Yeah, I've been waiting for 4 years on both those requests. I thought perhaps a bit of cross promotion of "permission based requests" might actually get some action happening from Clickup...
Tanner Wixom
Michael Van Doorn Thanks for clarifying. I didn't know that behavior was part of ClickUp's permissions system. But that makes sense. Understanding that now, I think your proposed MVP sounds good. Thanks again.
Gary Way
Michael Van Doorn Does this mean that a view can be shared with a user/team, and that is the only view they will see from the list?
We work closely with agencies and want to share a view of a list that's filtered to tasks that are assigned to them. Realise this can be done with 'Me Mode', but sometimes we want to be able to lock a view down so other tasks can't be seen.
Michael Van Doorn
Gary Way: Not necessarily as 'required' views (Always List view) cannot be made private.
Naomi Peters
Michael Van Doorn I would like to add an additional bullet point to your list...
View sharing options
Public
Private (just to you)
Private (shared to anyone who has access to the Hierarchy where the view exists)
-> Private (shared to
selected
users who have access to the Hierarchy where the view exists)Example: Joe, Tom, & Sally have access to a list that I've created. I want to create a view within that list that is only available to me & Sally. So this would be a view that is private, but NOT available to
anyone
with access to that hierarchy, but rather to selected
users with access to that hierarchy.Gary Way
Michael Van Doorn I think to make this feature useful, 'required' views would need to be made private, as Naomi Peters mentions below.
Load More
→