0
8 comments
Spot On Innovative Approach Stellar Advice

You can either directly assign people or share the task. The issue is that if anyone has parent folders or project access by either having the folder or project assigned to them or shared they will have access to any task with in those folders or projects. Hope that helps.

0
Spot On Innovative Approach Stellar Advice

Thank you Ryan. The problem is they will have access to all other tasks in those folder/project where  they don't need necessary access to thos.

I posted a feedack in the following link to suggest implementing a custom role where admin can configured access on task level or even on field level. 

https://help.wrike.com/hc/en-us/community/posts/360010696134-Need-custom-roles-to-make-fields-tasks-editable-for-particular-users-

0
Spot On Innovative Approach Stellar Advice
1
Spot On Innovative Approach Stellar Advice

Thank you Ryan. Correct me if I am wrong, i still don't see the new release can limited the task assignee's access to another task in the same project.  (The ideal way is the user should have Editor access to task he/she is assigned, but limited access to other tasks in the same project) Hope the future release will have that. 

0
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi Junpei, I'd love to know a little bit more about the process here.

For example, if you want to share some tasks with a client, but you don't want them to have access to all tasks in the Folder/Project, you could create a separate 'client' Folder, share it with the client and tag this Folder on tasks you want to be shared with them. Then, simply, every time there's a task you want to share with them, you can tag your client's Folder and they'll have access to see those tasks only.

Again, it would be great to hear what exactly you're looking to accomplish here by getting a little more detail so we can discuss other options 👍

0
Spot On Innovative Approach Stellar Advice

Hi Stephen,

Thank you for the feedback. We currently have department based folder structure (see fig. 1)

 

This is what we try to accomplish....

* Department Admin have full access to folder/project

* Department User have limited access to folder/project

* Other Department user/admin have no access to this folder/project

* Department Admin can assign task to anyone in the system.

* The assignee should gain access only to that particular task.

Please advise how we can archive this. 

0
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi Junpei, I see the obstacle you're facing now, thanks for coming back. 👍

This sounds like cross-functional collaboration within your company so I would still recommend using my suggestion above - just a little different.

  • Create a new Folder, let's say we call it, 'Collaboration Folder' and share this Folder with the person you need to cross-collaborate with and edit their permissions as needed. 
  • You can then create a task in your own Department Folder and tag this 'Cross Collaboration' Folder to the task. Then the task exists in both Folders.
  • However, the person you're working with will only be able to access the task in the Collaboration Folder, not the Department Folder, and they'll have the permission conditions you've specified for them in that Folder.
  • The person assigned will then have the task visible in the Collaboration Folder, but you have not shared it with them in the Department Folder so they can't see anything else in that Folder.

I've briefly explained this for each condition you've specified below. Please let me know if you have any questions at all 👍

* Department Admin have full access to folder/project:
This means you share the Department Folder with the admin with full access.

* Department User have limited access to folder/project:
Share with the User/User Group and edit their permissions to Limited.

* Other Department user/admin have no access to this folder/project:
Do not share the Folder/Project with anyone outside the Department. Perhaps look at setting up department based User Groups for easier sharing with large groups.

* Department Admin can assign task to anyone in the system:
Once the admin tags the 'Collaboration Folder' on task and shares this Folder with the person they want to assign (as outlined above), then that person will have access to the task from the Collaboration Folder, not the Department Folder - but it exists in both Folders.

* The assignee should gain access only to that particular task.
Because the person only has access to the task via the tagged 'Collaboration Folder' they won't be able to see any item from the Department Folder.

0
Spot On Innovative Approach Stellar Advice

Hi Stephen,

Really appreciate your detailed feedback. I see problem with using 'Collaboration Folder' the following: 

* If your project involve multiple teams, I believe creating 'Collaboration Folder' for each team is necessary because we want team see the tasks that are assigned to them only, If we create one 'Collaboration Folder' and put every collaboration team in that folder, i think team can access and edit other teams' tasks, that would defeat the purpose of the assignee should gain access only to that particular task.

* The number of folders will grow exponentially as time goes by as there many collaboration folders for each single project, and ultimately impact the loading speeding of the web page. 

 

0

Folllowing List for Post: Is there a way to limit user access on task level?
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post