See all BOEs without edit access role permission

Feature Request: View-only Access to BOEs on Accessible Proposals

Summary:
Introduce a role-based permission that allows users to view all BOEs associated with proposals they can access, while restricting edit rights to only those BOEs where they are explicitly granted access (e.g., via the RAM). This enables authors to reference relevant BOEs without expanding who can modify them.

Problem Statement:
Today, authors creating or updating a BOE often need information that resides in other BOEs on the same proposal (such as assumptions, inputs, rates, or scope details). If they do not have edit access to those BOEs, they typically cannot see them at all. This forces users to rely on email, chat, or offline documents to gather needed context, which is slow, error-prone, and difficult to audit. Granting full edit access solely to enable visibility introduces governance and quality risks, as more users gain the ability to change BOE content they do not own.

Proposed Solution:
Add a new permission that can be assigned to roles which grants view-only access to all BOEs on proposals the user can already access, without expanding edit rights.

• Users with this permission can see and open any BOE tied to an accessible proposal in read-only mode.

• Edit rights remain controlled by RAM-based or existing BOE-level access; users can only edit BOEs where they are explicitly listed with edit permissions.

• The BOE interface should clearly indicate when a BOE is read-only versus editable for the current user.

• Existing proposal-level security must remain intact: users cannot see BOEs for proposals they do not have access to.

Benefits:

• Enables authors to efficiently reference related BOEs when preparing their own, improving accuracy and consistency of BOE content.

• Reduces reliance on out-of-band communication (email, chat, documents) to obtain information from other BOEs.

• Preserves strong governance by limiting edit capabilities to appropriate users while still broadening visibility where needed.

• Decreases the risk of unintended changes to BOEs by clearly separating “view-only” and “edit” access.