I'd like to request a feature that allows for more granular control over user permissions within the Ideation section, specifically by splitting permissions into "View," "Vote," and "Comment," similar to the existing permission structure in the forum discussion areas. Basically, would like product parity for permissions between forums and ideation.
Current Situation:
Currently, the Ideation section permissions are "all or nothing." If a user has permission to access Ideation, they typically have full access to view, vote, and comment. This lacks the flexibility we require for our community management.
Desired Functionality:
We need to implement a permission system for Ideation that allows us to control "View," "Vote," and "Comment" permissions independently based on both primary and custom role. This would enable us to create custom user roles with specific access levels, like how it is in the discussions.
Use Case & Rationale:
Our community utilizes a multi-tiered user permission system. All registered users initially go through a screening process.
- "Registered users" (Primary Role): All users upon registration.
- "Role B" (Custom Role): Registered users who have passed the screening and are granted full posting permissions in forum discussions.
- "Role C" (Custom Role): Registered users who have not passed the initial screening and are limited to viewing content in forum discussions.
Currently, we can effectively manage these roles in the forum discussion areas. "Role C" users can view but not post, while "Role B" users have full posting capabilities.
However, this granular control is lacking in the Ideation section. We wish to extend the same level of control to Ideation. Specifically, we need to:
- Allow "Role C" users to view Ideation submissions.
- Allow "Role B" users to view, vote, and comment on Ideation submissions.
The current "all or nothing" approach prevents us from implementing this refined permission structure and may be impacting our support community’s SEO and discoverability.
