"Collaborator plus" handling

 Hello,

Is there any chance/option that I could add users to a project which just have the rights of a collaborator but I can see them in the workload. 

E.g. I do not want all engineers/PMs to be able to change the tasks, as this is the duty of the project leaders.

The collaborator plus should only have the possibility to add/change tasks in folders he has created. E.g. for his own specific time scheduling and reminders.

It would be great if an additional role could be added to your business model to have such a role with a specific price e.g. 10$. This would make it much more attractive. 

Regards

Andre

1
3 comments
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

Hi Andre, thanks for reaching out here! This is an interesting use case, thank you for taking the time to go over it. Based on the workflow you described, it sounds like Folder/Project Permissions could do the trick here. The idea behind this functionality is that you can limit editing rights on a per Project and Folder basis for team members who are regular users in your account. This means that they'll be able to create tasks in their personal Folders, but their editing rights in other selected Folders will be limited (like Collaborator rights). You will also see these users on the Workload, and they'll be able to track time for tasks. Would this work for you? Looking forward to hearing your thoughts about this!

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

There's another annoyance in the way that Wrike manage permisions.

We work in a magazine. Every issue is a project. Every project/issue has many tasks/sections with subtask (composing-revision-typesseting process of the secition).

I want everybody to see the "big picture" (sections list of the issue) buy I dont want, i.e., people from typesetting see some very long discusions happening during revision.

How to solve this problem?

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

Hi Luis, thanks for commenting here! This is a really interesting question, an we recently had a discussion with another member of the Community about ways to keep different types of communication separate, here's the post: Unsharing Subtasks of a Shared Task. It sounds like this is somethign that could help you, and I'd love to hear what you think about the approach there. Happy to continue this conversation and discuss other ways of managing visibility there!

0
Comment actions Permalink

Folllowing List for Post: "Collaborator plus" handling
[this list is visible for admins and agents only]

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