Project Roles: Frequently Asked Questions

This topic answers frequently asked questions about Project Roles.

1. Why am I unable to save the changes I made to permissions on an Asset/folder when I view it through the Project Roles?

   When you edit permissions on an Asset or folder, you are not modifying the Project Role. You are modifying permissions based on roles only for that folder and its contents. This gives you the ability to layer your permissions in a hierarchy throughout the contents of a Project.

2. Default Project Roles: Resource vs Team. Which takes priority?
   There are two separate default Project role fields in the system. One exists on the Resource, and one exists on the Team.

   Resource email	Tylor Spence, [e-mail]
   Default Project role	role1
   Teams	Tylor Spence is on the Marketing Team, which has a default Project role of role2.

   • Tylor Spence is added to a Project: Tylor Spence is assigned the default Project role of role1 (unless otherwise specified).
   • Marketing is added to Project: Tylor Spence is assigned the Team's default Project role of role2 (unless otherwise specified).
   • Both Tylor Spence and Marketing are added to the Project: Tylor Spence's permissions on the Project are a merger or role1 and role2. The higher permission is always used for each field in this scenario.

     If role1 and role2 have a value set to No, then Tylor Spence cannot perform the action. However, if either (or both) role1 or role2 has the permission set to Yes, then Tylor Spence can perform the action.