Flexible Access Tag Requirements for Proposal Submission

Feature Request: Flexible Access Tag Requirements for Proposal Submission

Summary:
Allow users to submit proposals to CE as long as they have at least one of the required access tags assigned to any item within the proposal, rather than requiring them to hold all access tags associated with the entire proposal. This change reduces friction for collaboration and streamlines the submission process.

Problem Statement:
Currently, a user must have all access tags assigned to the proposal in order to submit it to CE. This strict requirement blocks legitimate submitters who only need to work with a subset of items in the proposal. It creates unnecessary bottlenecks, forces additional admin intervention to adjust tags, and slows down proposal processing, even when the user’s access is sufficient for their role.

Proposed Solution:
Update the submission permission logic so that:

• A user can submit a proposal to CE if they have at least one of the access tags that is assigned to any item within that proposal.

• The system verifies access tags at the item level and aggregates them for the submission check, instead of requiring a complete match of all proposal-level tags.

• If a user attempts to submit a proposal with items they do not have access to, the system provides a clear message indicating which items are inaccessible and why, while still allowing submission if at least one qualifying access tag is present.

• Optionally, provide an audit-friendly record indicating which access tags were used to authorize the submission.

Benefits:

Reduces unnecessary access-management overhead for proposal submissions.

Enables more flexible collaboration, allowing users to submit proposals when they have partial but sufficient access.

Decreases delays and bottlenecks in getting proposals to CE.

Improves user experience by aligning permissions with real-world roles and responsibilities.: