I think it would be really awesome if you were able to have pre-determined project roles as a part of a template. Today, you are only about to assign a role once a user is added as a project-member. I think it would be powerful to know what roles need to be mapped.
Here is a screenshot demonstrating this:
- When creating a project from a template, assigning who will fill what role and adding any necessary additional roles would be great
- Be able to set permissions for users in a project based on the role assigned.
Thanks @Phil_Seeman. I didn’t do much digging to see whether this feedback was already provided or not.
The first link you provided pre-dates the introduction of Project Roles and Overview and seems to suggest how the role of TASKS can route assignments to users. Something I am interested in as well, but isn’t quite the same as what I am suggesting. I am thinking just for reference sake - knowing who is serving what role in a project from the Overview. That said, it could serve as the “routing table” if Asana was to allow you to assign tasks in a template to a role instead of a person.
The same goes for the 2nd link.
I think my feedback is maybe the first step to enabling what these other two posts are suggesting. Do you agree?
Well thanks, @LEGGO, now you made me go back and actually read the other 2 threads.
I do indeed! Your post adds the new dimension of project roles to the equation, so it’s definitely an addition to the idea and not repetitive of the others.
I think project roles could be part of the solution to being able to have roles as assignees in a template, and/or for permissions.
At the same time, I also think about the overall role(s) that one can define for a user in the user profile:
If a user is always going to have the same role in all templates, then instead of having to set that role in every one of their projects on the Overview, it might be nice to also have the option to define the role globally in the profile - yes?
@Phil_Seeman I do like that idea and thought the same. It works probably 80% of the time for us but not always. We have many people that play different roles on different types of projects. Also, depending on the project it may call for a uncommon role to be filled.
Additionally, there would have to be some layer of smarts to know which person is filling that role assuming many could. For instance, is this project a part of a particular region or market that suggests one user over another.
Being able to establish roles at the project level would be nice. I wouldn’t be opposed to when adding roles you could select from a list of unique ones in a org. This selection then offering a list of individuals defined as that role. All of this with the ability to create a new role or assign someone to a role that doesn’t otherwise match it heir profile.
I think being able to first define roles to be filled in a project template is a great start. So much more that could be built off that possibility.
Oh man, I just realized that with Project Roles you could do some really powerful things with Rules. For instance, when certain triggers are met specific individuals could be assigned or set as collaborators based on rule assignments. You wouldn’t have to define the individual but rather rely on the role mapping to route to them.
I added my vote to this one. I think @LEGGO you are on to something here. Hope this could be considered in the future.
Thanks for providing this feedback @LEGGO and for adding some additional context @Phil_Seeman and @Paul_Grobler! Roles being included templates would be
We’ll pass this onto our Product team and hopefully it is something we can see brought to life in the future! I’ll keep you all posted
@LEGGO just to be clear, I didn’t mean to suggest to use the profile role in lieu of project roles. My point is it would be cool to be able to use them both. Perhaps profile roles would be the “base” but could be overridden by a project-specific role.