> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Elastic signing concepts

> Learn about the basic concepts and objects used in elastic signing.

This page describes the basic concepts used in elastic signing.

## Elastic templates

The Click API is built around a core object called an *elastic template*. An elastic template is an iframe that displays your terms to your customers for them to review and accept. You can display an elastic template as a modal (a window positioned over your page), or inline as part of your page.

An elastic template may record agreements from multiple users. Each time a new user accepts the elastic template, that user agreement is stored with the elastic template object.

## Elastic template versions

Docusign automatically versions your elastic templates. The first elastic template you create becomes version 1 (**V1.0**). Updating an elastic template automatically creates a new version (**V2.0**, and so on). You can configure your elastic template settings to prompt users to agree to the updated terms the next time they log in.

The version number for each elastic template displays in the **Version** column on your dashboard in the UI, as shown in the following image:

![The My Elastic Templates page displays the version number of each of your elastic templates.](/_fern-files/_img/134600d7cfd4415ef3b005a2883ed9243b3be6645c5b31765573b591c667fa73.webp)

An elastic template can have any number of versions. When you edit an elastic template, you can choose to edit an existing [draft](/docs/click-api/click101/managing-elastic-templates#draft-elastic-templates) of that template or, if your chosen template does not already have a draft, one will be created for you automatically. If you save your changes without activating, the draft will be saved and your changes will persist to the next time you choose to edit the elastic template. Only the most recent version of the elastic template can be active.

## Client ID

When you create an agreement from elastic template, you specify a `clientUserId` that uniquely identifies the agreement's user. This value can be any identifier that your own system uses to track individual users. Examples include employee IDs, email addresses, and surrogate key values. The Click API uses this identifier in combination with other information to determine whether a user has already accepted the agreement, and also to report on user responses.

## Next steps

* [Click API 101](/docs/click-api/click101)
* [Rules and resource limits](/docs/click-api/click101/rules-and-limits)