Skip to Main Content
ProPricer BOE Pro Ideas
Status Future consideration
Created by Guest
Created on Feb 18, 2026

Restrict Copying and Library Saving for Contract-Specific Proposals

Feature Request: Restrict Copying and Library Saving for Contract-Specific Proposals

Summary:
Add a configurable setting that prevents users from copying tasks and BOEs from certain proposals and from saving those proposals’ BOEs to the shared library. This will ensure that contract-specific or sensitive proposal configurations are not reused inappropriately on other bids.

Problem Statement:
Some proposals contain contract-specific data (e.g., unique terms, rates, or scope details) that should not be reused on other proposals. Today, users can copy tasks and BOEs from any proposal or save BOEs from those proposals into the library. This creates the risk that contract-bound or sensitive structures are inadvertently applied to new proposals, causing compliance issues, pricing inaccuracies, and additional rework to correct misapplied data.

Proposed Solution:
Introduce a proposal-level setting or flag (e.g., “Contract-specific – do not reuse”) that, when enabled:

  • Prevents copying tasks and BOEs from that proposal into other proposals.

  • Prevents saving BOEs from that proposal into the shared BOE library.

  • Optionally displays a clear warning or tooltip explaining that the proposal is contract-specific and cannot be used as a source for reuse.

  • Ensures that users can still fully edit and manage tasks/BOEs within the flagged proposal itself, without impacting its internal usability.

  • Allows administrators to configure who can toggle this setting and to apply it by default for certain proposal types or customers, if needed.

Benefits:

  • Reduces the risk of reusing contract-specific or sensitive proposal data inappropriately.

  • Improves compliance with contractual and regulatory requirements.

  • Minimizes errors and rework caused by applying incorrect BOEs or tasks to new proposals.

  • Gives organizations finer control over what proposal content can enter the shared library or be reused.

  • Increases user confidence that reusable library content and copyable proposals are safe and generally applicable.

  • Attach files