Feature Request: BOE Read-Only Visibility for All Users
Summary:
Allow organizations to configure proposals so that all Basis of Estimate (BOE) records associated with a proposal are visible as read-only to all users, regardless of RAM assignment. This includes a system-level default setting to control whether proposals expose all BOEs by default.
Problem Statement:
Currently, users can only see BOEs on a proposal if they are explicitly assigned in the RAM or by a RAM Admin. This restriction makes it difficult for authors and other team members to review historical BOEs across proposals for context or reference. As a result, users must rely on RAM assignments or ad hoc workarounds to access prior BOEs, which slows down authoring, reduces transparency, and limits the reuse of prior work.
Proposed Solution:
Introduce a configuration option that allows proposals to expose all associated BOEs as read-only to all users, independent of RAM assignments.
Provide a system-level default setting in administration/system settings that determines whether new proposals default to “BOEs visible to all (read-only)” or retain the current restricted visibility.
Allow proposal-level overrides so that admins or proposal owners can enable or disable “BOEs visible to all (read-only)” for specific proposals when needed.
Ensure that read-only access prevents users from editing BOEs unless they have appropriate permissions via RAM or other existing controls.
Clearly indicate read-only status in the UI so users understand they are viewing reference material and cannot modify it without elevated permissions.
Benefits:
Enables authors to quickly look up and reference past BOEs to understand prior work and estimates.
Improves knowledge reuse across proposals, reducing duplicated effort and inconsistencies.
Increases transparency by making BOE history broadly visible while still protecting data integrity through read-only access.
Reduces administrative overhead tied to RAM assignments purely for visibility purposes.
Enhances user productivity and confidence by providing consistent, system-wide behavior controlled via a default setting and proposal-level overrides.