Remove a User's access without removing them from Workspace
E
Erik VM Hatfield
I would like the ability to lock a user out of the Workspace without removing them from ClickUp. Ideally, this would also change the account type to View Only Limited Member that would not count against paid user seats.
This would work in conjunction with being able to clone a user's access so that when a user leaves the company we can lock their account and then when a new user is assigned to the position, they can instantly be assigned all the previous user's tasks.
Log In
James Hogg
The Offboarding process in ClickUp is woeful. Basically the Enterprise UNFRIENDLY design means tasks can quickly be lost.
Here we are removing a User. All we get is their tasks will remain and not be deleted, but no offer to prevent tasks being ORPHANED in lists that user could only access. WHERE ARE WE SUPPOSED TO FIND THOSE TASKS?
It is often not viable to have a handover of tasks from one user to another in an ordered fashion, where outgoing employee assigns tasks over to new employee. Maybe ClickUp is too young a company to have had to deal with instantanious offboarding needs, such as an instant dismissal or employee death, or where (as Erik VM Hatfield aludes to) a new Hire to replace role has not yet been made.
If ClickUp wants to continue down the route of having Personal Tasks and users having rights to make Spaces, Lists or Tasks "Private" and giving an Enterprise no Global Super Admin role that has visibility to Tasks or continue to allow Space Owner's to be excluded from Tasks in their own Space (which is ludicrous), then at least give us a Dashboard View where a Super Admin can see all "Orphaned" (not assigned, but in List only available to Removed Users) and "Assigned to Removed User" Tasks for reallocation. Surely having tasks not accessible to any active User or assigned to old Users is in no Workspaces interest?
Armine Seropyan
Thank you for your suggestion. Could you clarify why you need to lock a user out of the Workspace without removing them? Trying to understand the use case better.
E
Erik VM Hatfield
Armine Seropyan
Hello,
The idea is that when a user leaves the company or goes on a Leave of Absence we would lock their account so they could not access our Workspace.
In the case of a LOA they would be unable to access their account, but, it would be preserved for their eventual return.
In the event a user leaves the company this feature would go hand in hand with another feature request I have submitted to clone a user's access. Example: a user leaves, we lock them out of the workspace, when a replacement is hired we would then clone the leaving user's access and assignments to the new user. Then we would then delete the leaving user's account.
When you lock someone out of their account it would move them to a View Only Limited Member user role or similar.
Yes, we could assign each person to a TEAM for their position and then put the new user in the team. But that is a really clunky work around... There would be a lot of confusion as to whether to assign tasks and comments to the person or the team... and, using the TEAM name when assigning to a single person kinda makes that user feel like a number, that they only exist as their position or we're expecting them to leave... It doesn't feel inclusive...