Gosh thank you ! I will try this. Borderline panic here. I tried for almost 30 minutes to create a support ticket, and all I would receive is “I apologize for not being able to assist you 
. Could you please rephrase your question so that I can provide better support?” so I reached out to @Eileen_Hwang to see if I could possibly receive the same level of support that you did. Our team is basically frozen. Two of us are super users and not even able to change ourselves from team admins in public projects. I hope I get some help.
Note: Elevating a key reply which may be a solution for some
I haven’t confirmed this personally, but according to @Alison13:
If that’s the case, then your Super Admin can contact support directly with these steps to make the request.
Thanks,
Larry
1 Like
@Phil_Seeman - do you know if this is still accurate? I haven’t seen anything in the documentation about it changing, but not sure if I missed anything. This feels extremely important.
I haven’t tried it yet, and the update operation is not documented, but supposedly you can now update a user’s project role via the API:
2 Likes
It’s true that it’s available, but we’ve noticed some issues with the documentation (and possibly a bug wit update) that we are working on fixing this week. Sorry about that.
3 Likes
All–Can someone help me understand, please, what this icon represents? We have a project where we want to restrict certain user’s ability to edit aspects of the Asana project. We configured some as Commenters, but it seems there are “shades of grey” for the Commenter status (see pic)…?
Questions:
- How does one end up with the caution icon?
- How is the Commenter + caution icon different from Editor?
- Is it possible to intentionally configure the permissioning this way?
- What other technical considerations should be know about when seeing this icon?
Thank you!
@Adam_Caruso - if you hover over that 
, I think it should give you a tooltip. The gist is: with the introduction of team sharing, there are now 2 ways a person might gain access to a project: as a member of a team or directly. If a user is in a team with a higher permission level than they individually have, the will appear to indicate that.
I believe you receive the highest level of permission available to you either individually or through a team. So, if you are in a team that has editor access to a project but you individually are added as a commenter, you’ll see that warning and receive editor access (via your team).
Tracking all, thank you. We had users report inconsistent experiences with how they could interact with the target project, though.
Example:
User A and User B were both “Team Admins” in their respective teams. Both were set as Commenter roles in the target project. But only one of them had the ability to edit the target project (to direct multi-homing, etc.).
I’m curious what setting is driving the nuance in these permissions…
Thoughts?
@Adam_Caruso - their level within the team shouldn’t matter, as all members of the team will receive the same permissions if the team is added to a project. Are their teams added to the project with the same permission level?
Example:
- User A is in team 1, user B is in team 2
- Users A and B are both added to Project as commenters
- Team 1 is added to Project as editors, team 2 is added to Project as admins
- User A will be an editor in the project and B will be an admin (both via their team, as that is the highest access level available to them)
- If user A were added to team 2, they would then also become an admin on the Project
As far as what people can do, you can find more here (additionally, there’s an option on each project to determine what editors vs. admins can do):
1 Like