Expand Allow Estimate Level to RAM Group

Feature Request: Expand Allow Estimate Level to RAM Group

Summary:
Enable configuration of the BOE estimate level (Task or PBS) at the RAM group level so that different user groups (e.g., engineering vs. material estimators) are required to enter estimates at the appropriate level for their workflow.

Problem Statement:
Currently, the estimate level (Task or PBS) cannot be enforced per RAM group. All users must follow the same estimate-level setting, regardless of their role or responsibilities. This leads to inconsistent BOE entry practices, inefficiencies when users work at the wrong level of detail, and increased risk of errors or rework when estimates need to be realigned to the correct structure.

Proposed Solution:
Allow administrators to define the BOE estimate level (Task or PBS) as a setting on each RAM group.
When a user in a given RAM group creates or edits BOEs, enforce the group’s configured estimate level (e.g., Task level for engineering, PBS level for material estimators).
If a user belongs to multiple RAM groups, apply a clear precedence rule or require the user/admin to select the applicable RAM group context for the BOE.
Update validation and UI messaging to prevent users from entering BOEs at an estimate level that is not allowed for their RAM group.
Ensure the configuration is auditable and easily adjustable by administrators as team structures or processes change.

Benefits:
Aligns estimating practices with role-specific workflows (e.g., engineering at Task level, material estimators at PBS level).
Reduces data inconsistencies and rework caused by BOEs being entered at the wrong level of detail.
Improves governance and process control by enforcing estimate-level standards per RAM group.
Enhances user experience by guiding users to the correct estimate context based on their role.
Supports scalable, multi-team implementations where different disciplines need different estimation granularity.