> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/documents.md).

# Documents

Many events need people to sign a contract before they start working.

Documents is a great place to do this fully digitally.

### Create a new document

When creating a new document you have to give it a name and pick a category.

{% hint style="info" %}
A category contains the possible receivers of the document, like

* members
* groups
* visitors of a list form
* ...
  {% endhint %}

### Description

The description is something that is shown where the document name shows up on the platform.

### Body

The body of the document is the actual text that is going to be aggreed to by signing it. This is translatable in the supported languages of the platform.

#### Variables

The body of the document allows you to add variables to the text. These variables will be replaced by actual values when the document is opened by the user.

<details>

<summary>Examples of variables</summary>

<table data-header-hidden><thead><tr><th width="226.33203125"></th><th></th></tr></thead><tbody><tr><td><code>{{name}}</code></td><td>The name of the user</td></tr><tr><td><code>{{today_with_day}}</code></td><td>The current date when the document is going to be signed</td></tr><tr><td><code>{{company}}</code></td><td>The company of the user</td></tr><tr><td><code>{{email}}</code></td><td>The email address of the user</td></tr><tr><td><code>{{all_available_days}}</code></td><td>All the days the user is available for the event</td></tr><tr><td><code>{{bank_account}}</code></td><td>The user's bank account number</td></tr></tbody></table>

</details>

You can find more variables under the body text area. Read more [here](/event/misc/variables.md).

#### Formatting

Under the body text area there is another button where you can find formatting details. Formatting allows you to use titles, hyperlinks, bold & underscored text, etc. Read more [here](/event/misc/text-formatting.md).

#### Settings

You can also edit document settings like where to show it and if the event logo should be printed on the top.

#### Filter

Certain documents are intended for access and signature by a specific group of individuals. Moving forward, you can apply [a filter](/event/general/filters.md) to your document to ensure only these selected people have access. If you mandate that the document must be signed before the ticket can be downloaded, the system will intelligently enforce this requirement solely for those identified by the filter.

You can also add a custom message (translatable per language) that will be shown to anyone who opens the document URL but does not match the filter. If no custom message is set, a default explanation is shown.

## Signing

As stated above, these documents can be signed. If you share the URL of the document with the user they are redirected to a page where the document is displayed with a signing zone at the bottom.

<figure><img src="/files/8ihCe1x0xs3lQMBrXPAi" alt="" width="354"><figcaption><p>An example of the signing zone of a document.</p></figcaption></figure>

If on a touch screen (phone, tablet) the user can sign using their finger. On a normal computer they can use their mouse.

{% hint style="info" %}
Documents can be [signed](/event/accreditation/check-in-out/document-signing.md) digitally on our platform.

But sometimes you have a less tech-savvy person who prints out the document, signs it manually, takes a picture and sends it back to you. This way you can upload that picture and the document will be marked as signed.
{% endhint %}

## How to's

* [Preview document signing process](https://docs.eventication.com/event-how-to/preview-document-signing-process)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eventication.com/event/general/documents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.