All Collections
Best practices
How to build a GetAccept Editor Template
How to build a GetAccept Editor Template

A guide based on best practise of how to build a GetAccept editor template

Updated over a week ago


  • Templates can be described as frameworks for signable documents or presentations. Templates contain relevant information for the senders to share with recipients.

  • If you already have a Word/Google Docs template, you can easily create a GetAccept editor template using the same text content you have in your existing templates. However, there are engaging elements that you can add to build a dynamic template.

  • Templates can be selected by users, and you, as an admin, can decide what content of the template can be edited by the users.

  • You can set up a specific signing order in the template, ensuring that the sender doesn't forget to add the recipients according to the process.


  • A template can be built with resources, allowing you to add the same resource to multiple templates. Then, you have one place where you need to edit the content, and it will be updated across all connected templates.

  • A resource can be a piece of content that is not always relevant to share with the recipient, so it's not included in the template itself. Instead, you're building a library of resources, making it easy for the sender to add the relevant content to the selected template.

Example of how a template can be built in the GetAccept editor

In the video you can see some of the elements being added to the template:

  • Video block

  • Image

  • Image & Text

  • Text input (text fields)

  • Pricing table

Template roles

Do you want to automatically add recipient data to the template?

Does your process require a specific signing order for your documents?

Create template roles to achieve efficiency by automatically filling in names, email addresses, and company names into the template, and by having any required signing processes predefined.

Did this answer your question?