Stephanie Morgan
posted this on October 13, 2011 02:23 pm
We have spent a great deal of time honing in and simplifying our permission set. Below is a breakdown of what each permission type means and how the roles affect a user.
Project Manager
A Project Manager is the person 'leading' the project. You have the option, at project creation, of changing the project manager of the project. This person will be included in any emails that go to people that have an upcoming or overdue resolution. Also, project managers are notified via email when someone completes a resolution.
Permission Controls & Roles
We have spent a great deal of time honing in and simplifying our permission set. Below is a breakdown of what each permission type means and how the roles affect a user.
Project Manager
A Project Manager is the person 'leading' the project. You have the option, at project creation, of changing the project manager of the project. This person will be included in any emails that go to people that have an upcoming or overdue resolution. Also, project managers are notified via email when someone completes a resolution.
Permission Controls & Roles

Per this example, you can see the different permission options that exist within a project. These settings are originally defined during the project creation process but can be modified under 'Settings > Access Control' area of the project you want to update.
Here are a breakdown explanation of each role:
Full Access - Just like it sounds, these users can access all features of the project.
Responder - Responder only allows users to respond to recommendations under the 'Rec' tab.
Read Only - Read Only users can view the project but will be unable to make any changes to any of the projects.
No Access - They will not be able to see this project at all when they login by choosing this option.