Understanding Document Templates and Versions
Why templates are versioned, and how your church gets its own copy the moment you customize one.
Why templates are versioned
Every time a template's layout or content changes, Sermfy keeps the previous version rather than overwriting it. This means cards already generated under an older layout remain visually consistent with when they were issued.
System templates vs. your church's templates
Sermfy ships system templates (like the default Classic Membership Card) that every church starts with. The first time your church customizes one, Sermfy "forks" it into your own tenant-specific copy, your edits never affect the original system template or other churches.
This fork-on-save behavior is automatic, you don't need to explicitly "duplicate" a template before customizing it.
Where to see version history
Template settings show the version currently active for new generations, older versions remain associated with any documents already generated from them.
Related Articles
Bulk-Generating Membership Cards for Multiple Members
How bulk card generation processes in the background, and what happens if one member's card fails.
Customizing Your Membership Card Template
What you can and can't customize today, and how changes are saved.
Troubleshooting a Membership Card That Won't Generate
The most common reasons a single card fails, and how to fix each one.
Why Document Generation Happens in the Background
Cards and certificates render on a dedicated background system, not instantly in your browser.