General permissions must be configured for resource permisions to have relevance

• Type: Feature Request
• Status: Under Review
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: User Management > Roles
• Labels: None

Summary

General permissions must be configured for resource permissions to have relevance.

Description

The current way in which permissions are structured can be confusing for admins. To illustrate, imagine creating a new "web content reviewer" role. When defining permissions for that role I  might skip over the "general permissions" section thinking that I simply need to give the user access to "resource permissions." However, if I did so, the assigned user would not be able to access the administration panel at all, leaving them with no way to access web content and the resources that they have been given permissions for.

Proposed Solution

Adding a web content resource permission such as "add web content" should automatically assign the role at least the "view" and "access in site and asset library administration" general permissions (but not vice versa).