Currently, Alma does not store version history for XSL templates used in letters. This creates risk: if a change introduces errors, there is no easy way to roll back.

I propose adding version history functionality - similar to the “View Versions” feature in the Metadata Editor - so staff can revert to earlier versions when needed. Ideally, previous versions could also be labelled for clarity.

This enhancement would:

1. Reduce the risk of breaking live communications with untested changes.

2. Eliminate the need for external tracking in GitHub or personal repositories.

Adding version control would make template management safer, more efficient, and fully integrated into Alma.