Update Role Permissions about vulcan HOT 6 CLOSED

Also should investigate https://github.com/varvet/pundit as a potential alternative to rolify here, pundit seems more up to date and provides nice separation between permissions and logic.

from vulcan.

We need to consider the additional roles:

• Editor - ability to edit comment and mark controls as needing a review, no ability to sign-off or approve
• Reviewer - ability to approve of changes to a control, request changes
• Project Admin - full control over a project including locking discussions, reverting controls to previous state, users management of their project

from vulcan.

No need to implement Organization, maintainer, Sensitive roles

from vulcan.

Users have an overall roll for Vulcan that allows them to perform certain actions (TBD, but some examples may be full administration, creating new projects, importing SRGs, etc.)
Users have a project specific role that allows them to, for example, Lock/Unlock controls added to that project, revert a control to a point in history, etc.

from vulcan.

Users have an overall roll for Vulcan that allows them to perform certain actions (TBD, but some examples may be full administration, creating new projects, importing SRGs, etc.)
Users have a project specific role that allows them to, for example, Lock/Unlock controls added to that project, revert a control to a point in history, etc.

@Bialogs @rbclark Am I reading this correctly as 1 role per user and 1 user per project?

from vulcan.

1 App level role per use and 1 project level role per user (2 "roles" total)

from vulcan.