Organize
Build a document process once and give your team a reliable way to repeat it
5 capabilities
Templates let your team package a document process once and reuse it everywhere. Routing rules, expiry settings, authentication, and participant behavior all live inside the template, so every copy that goes out follows the same setup. Admins can limit what recipients see, apply retention rules, and handle compliance requirements without reconfiguring each send. Every template keeps its own history, versions, and audit trail, so you can always trace what changed. Because the configuration happens once, high-volume work moves faster and with fewer mistakes. It's a good fit for HR onboarding, enterprise applications, and multi-step approvals where consistency counts.
Decide how long each template stays active before it expires or moves to the archive, so no one reuses an out-of-date version by accident. This matters most in audit-driven work where a document's validity has a shelf life, and it keeps every app's workflows consistent.
Control what recipients can see, edit, or sign. Restrict specific fields, hide sensitive details, or make certain entries mandatory; the permissions are yours to set. Recipients follow the path you intend, which keeps the data accurate and protected.
Set the sending behavior (routing, sender identity, notifications) right on the template. From then on, sending follows the same standardized process without anyone re-entering settings. That predictability pays off for teams handling the same task over and over.
Add verification such as OTP or email checks before a template can be opened, so only the intended recipient gets in. You can dial the verification level up or down depending on how sensitive the document is.
Every template action, from creation to modification to publishing, is logged, and version history shows exactly who changed what and when. That record keeps templates accountable and makes audits far less painful.
Set up the documents, routing, and rules once. Every send from that template follows the same process without re-entering settings.
Upload PDFs or attach forms you built in FormWiz. A template can hold one file or a full packet, such as an offer letter with policies and tax forms.
Choose who receives the template and in what order. Assign roles so each person only sees and completes their part.
Decide how long the template stays active and how long completed records are kept. Expired templates close on their own so old versions are not reused by mistake.
Limit what signers can view, edit, or download. Hide sensitive fields or require certain entries before the document can move forward.
Save the template for your team. Each send uses the same setup, and version history shows what changed if you update it later.
Clear answers about building templates, version history, recipient rules, and sending the same workflow again.
A template is a reusable package for a document process. It holds the files, signer routing, expiry rules, and access settings so every send follows the same setup.
Yes. Updates create a new version in the history log. Sends already completed keep their original record; new sends can use the updated version once you publish it.
Yes. Every edit is logged with a timestamp and the user who made it. You can see who changed routing, fields, or policies and when.
Yes. Add an email check or OTP on the template so only the intended recipient can open and complete it. You can tighten or relax that based on how sensitive the document is.
Yes. Templates live inside each application workspace, so teams or brands can maintain their own library without mixing content.
Didn't find your question? Ask us directly
More capabilities that pair well with Signing Templates
Keep brands, branches, and departments separate without juggling accounts
Learn moreOrganizeConfigure a dedicated workspace for each brand, business unit, or region
Learn moreCollaborateKeep documents protected, organized, and easy to track from start to finish
Learn more