I'm submitting this enhancement idea on behalf of my strategic client, FEI Systems.
Overview
• FEI Systems is actively using Responsive Projects to manage collaborative content development across multiple user roles
• Section descriptions and help text fields are designed to provide critical context and guidance for completing questions within a section
• These fields currently function as shared instructional content but lack appropriate governance controls
Current Challenge
• Authors, reviewers, and guest contributors can edit section descriptions and help text fields when assigned to questions within a section
• This behavior appears to be an unintended gap in permission enforcement
• Allowing broad editing access creates risk of inconsistent, inaccurate, or overwritten guidance across sections
• Changes to these fields can negatively impact content quality, user understanding, and overall project integrity
• There is currently no mechanism to restrict or audit who can modify these critical instructional fields
Proposed Enhancement
• Introduce role-based permission controls for editing section descriptions and help text fields
• Restrict editing access by default to admins and project primary contacts
• Provide configurable permission settings that allow designated roles to grant or revoke edit access for additional users such as authors, reviewers, and guest contributors
• Include visibility into who last modified these fields through audit history or change tracking
• Ensure permissions are consistently enforced across all project entry points where these fields can be edited
Expected Impact
• Improves governance and consistency of instructional content across projects
• Reduces risk of unintended or unauthorized changes to critical section guidance
• Enhances trust in the accuracy and reliability of project content
• Provides administrators with greater control and flexibility over collaboration workflows
• Aligns platform behavior with expected enterprise-grade permission standards
