The ability to enable and disable auto calculations at the proposal properties/template level.

Feature Request: Auto Calculation Toggle at Proposal Template Level

Summary:
Add the ability to enable or disable system-driven auto calculations at the proposal properties and template level, allowing administrators and power users to control when calculations run versus when values are entered or maintained manually.

Problem Statement:
Currently, auto calculations are applied uniformly, regardless of the specific proposal context or template. This can be problematic when certain proposals require custom overrides, fixed values, or scenario-specific adjustments that should not be recalculated. Users may have to repeatedly correct or re-enter data that the system recalculates, leading to frustration, reduced trust in the system, and increased risk of errors when manual workarounds are used.

Proposed Solution:
Introduce a configurable setting at the proposal properties/template level that allows auto calculations to be toggled on or off.
Allow template owners/administrators to define the default auto-calculation state (enabled or disabled) for new proposals created from that template.
Provide granular control, where appropriate, to enable/disable auto calculations for specific groups of fields (e.g., cost, schedule, risk) rather than forcing a single global behavior.
Ensure that when auto calculations are disabled, user-entered values remain stable and are not overwritten by background processes.
Include clear UI indicators showing whether auto calculations are currently enabled or disabled for a given proposal, with tooltips or help text describing the implications.

Benefits:
Reduces rework by preventing unwanted overwrites of manually curated data.
Improves flexibility to support a broader range of proposal scenarios and customer requirements.
Increases user control and trust in the system’s behavior around calculations.
Helps organizations standardize best practices per template while still allowing exceptions where automated calculations are not appropriate.