Archive and Restore for Proposal Templates

Feature Request: Archive and Restore for Proposal Templates

Summary:
Introduce the ability to archive and restore proposal templates, enabling teams to manage template lifecycles more flexibly across one or multiple BOE Pro instances. This capability should support temporary removal of templates from active use while preserving them for future restoration and reuse.

Problem Statement:
Currently, BOE Pro only supports copying proposal templates. Teams that manage a large number of templates, or that operate across multiple BOE Pro instances, lack a structured way to retire templates that are not in active use without permanently deleting them. This becomes especially problematic when using the "Update from Template" feature with imported proposals, as there is no clean mechanism to manage older or environment-specific templates over time. The result is cluttered template libraries, increased risk of using outdated templates, and limited control over how templates move between instances.

Proposed Solution:
Introduce an archive/restore lifecycle for proposal templates with the following capabilities:

• Allow users to archive templates so they are no longer available for selection in new proposals or for the "Update from Template" operation, while preserving their data.

• Provide a dedicated view or filter to see archived templates and manage them separately from active templates.

• Support restoring archived templates back to an active state, making them immediately available for reuse.

• Ensure that archived templates remain compatible with imported proposals and multi-instance workflows (e.g., templates moved from one BOE Pro instance to another can be archived in one environment and restored in another when needed).

• Maintain referential integrity so that existing proposals created from a template continue to function as expected, regardless of whether the source template is active or archived.

Benefits:

• Improves governance and organization of proposal templates by allowing teams to retire unused or legacy templates without deleting them.

• Reduces clutter in template selection lists, minimizing the risk of users accidentally choosing outdated templates.

• Supports multi-instance environments by enabling templates to be moved, archived, and later restored as needs change over time.

• Increases flexibility for teams using "Update from Template" with imported proposals, ensuring only relevant, curated templates remain active.

• Preserves historical templates for audit, reference, or future reuse, enhancing long-term maintainability of proposal assets.