The advanced section can be found at the end of the sidebar of a template. It allows users to control how documents are managed after they are generated from a template.

There are different options to set customised preferences for the specific template. For example, users can set automatic document naming using questionnaire answers, route generated documents into the correct folder by default, restrict download before signature, share the questionnaire externally, and more.

The contents are divided in sections and users can use the search bar and type key terms to find what they are looking for.

This section contains the following items:

This allows users to automatically name the document using the extracted value from a Placeholder. For example, using the output of the “Company Name” Placeholder to name a document like Board Minutes. E.g. Acme Limited – Board Minutes

To trigger the display of the available placeholders, use ctrol+Space into the text field and a list will display all of the available options. The field will display similar to the below:

{{'Att':'Name of Placeholder'}} – Name of Document

Participants to be added/updated to related documents by default

You can check more information and step-by-step guidance about how to add an automatic document name here

This allows users to compare generated documents of the template to the baseline template it was created from.

The document editor will appear in right-to-left and support right-to-left typing, this can be useful for certain languages like Arabic. This is a template-wide setting. If only certain lines or paragraphs in your template require right-to-left formatting, you can apply them by clicking the

buttons under the ‘Home’ tab of your template editor when your text cursor is positioned at the line.

A new advanced template setting now allows you to default all conditions to “Trigger If Not Answered” (TINA). This setting streamlines template setup by automatically applying TINA logic to all conditions—meaning any unanswered question will trigger the associated conditional text by default. This is especially useful for templates with fallback or optional clauses, where you want to ensure key provisions are included unless explicitly excluded. By enabling this option, authors can reduce manual configuration, speed up testing, and avoid missing logic in complex questionnaires.

Allows the user to choose which mode the loops resolve in. More information about the modes can be read on this article: Modern and Legacy Modes for Loops

Allows the user to select the questionnaire style for its live demo whether it's the legacy style or new style.

In the Advanced section of the template, users could choose to enable/disable document Live Preview from the questionnaire page.

Whether track changes should be shown on the first draft. The other option is to show track changes in the document when it is first sent to the counterparty.

The two options basically speak for themselves, but in essence, these options allow you to modify a datasheet from the questionnaire.

As stated, this allows the questionnaire to be sent to external recipients as a form. More information about external forms can be found in this article: Sharing an External Facing Questionnaire from a Document.

Allows the user to choose a default folder destination in “Drive” once the document has been created

Allows the user to choose a default folder destination in “Drive” once the document has been signed on the platform.

If this is selected, you will turn off emails relating to the template. A drop down will appear where you can select which emails are not sent (including if that is all of them).

Custom email to counterparties on sending the document.

Use the custom email templates, if they are selected in the above settings, instead of sending them the default “You have received multiple documents” email.

Disables adding a custom message when sending the document to the counterparty.

Users are able to create templates from the current template after being archived, either by duplication or made as a related document.

Stop users from editing their rights on generated documents.

Users to be added to related documents by default.

By default, counterparties will be sent to the document questionnaire on templates created after August 2021, and the document editor for templates created before then. You can use this setting to select where they should be redirected to.

Do not require users added to the document on the counterparty side to sign up and create an Avvoka account. Participants who have been invited into a document can be restricted to only gain access to the document via guest access. Read more about guest access here.

Unanswered placeholders will no longer be replaced with blobs "[.]" on export.

Allows users to select the relevant header and footer style for their templates. Please refer to this article on how to create custom headers and footers.

Hidden data from clauses are inserted into the document allowing more accessibility and readability by AI tools.

The document is exported with field codes allowing it to be reimported into the system all the while preserving its data.

Allows the document to be exported as a PDF file along with its data as long as there are matching attributes. Read more about this in the article about Automating a PDF file.

These are options that allow/restrict the document from being downloaded either as a PDF or Docx file until it has been signed or completed.

The last option will only make the previous statements restrictions apply to the counterparty.

In this tab, users can manage metadata, search for a property on Microsoft Word and modify its Content Type.

Allows which attributes can be exposed for webhooks which allow an organisation's webhooks to access the selected attributes.

As the title suggests, it will display the documents character count on the generated document editor.

Limits number of characters allowed in the document's title and body, respectively.

Activates character auto-replacement rules that are set at the Organisation-level, within the generated document.

Allows specified whitelisted characters in the document body. This can also be applied t the document's title.

You can select specific roles that have permission to enable/disable any of the character validation rules stated above.