> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowsign.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Flowsign is one word with a lowercase s.
> The REST API base URL is https://my.flowsign.app and every endpoint lives under /api/v1.
> When answering API questions, cite the HTTP method and endpoint path.
> API access needs the Enterprise plan and an API key with the API access permission.

# Release labels

> What Experimental and Coming soon mean when you see them in Flowsign.

Some parts of Flowsign carry a small label so you can tell at a glance how finished they are. The label sits beside the feature it describes, and hovering it gives you the short version.

## Experimental

**Experimental** means a feature is available to use now and is still being shaped. Three things hold while it carries the label:

* **How it works may change as we improve it.** Screens, wording and options can move as we learn how the feature gets used.
* **Anything you have already sent or had signed is not affected.** A change to a feature never reaches back into a package that has gone out. How long completed documents are kept is set by your organisation's [data retention](/guides/settings/security) setting.
* **We want your feedback.** Tell us what is working and what is not through [Support](/guides/account/support).

Today the label appears on dynamic documents, in three places:

* The **Dynamic editor**, in its top bar.
* The **Dynamic** card in **Add a document**, where you choose between Standard and Dynamic.
* The **Dynamic** badge on document rows, in packages and in templates.

<Note>Dynamic documents need the **Enterprise** plan. See [flowsign.app/pricing](https://flowsign.app/pricing).</Note>

## Coming soon

**Coming soon** marks something that is planned and already visible in the app, but not usable yet. Its controls are shown and disabled, so you can see what is on the way instead of wondering whether you have missed a setting.

Today the label appears in two places:

* [Support](/guides/account/support): **Support tickets**, where **New ticket** is disabled while in-app ticketing is on its way. Until then, the contact form is the way to reach us.
* [Integrations](/guides/settings/integrations): the integrations we have not opened up yet, such as SharePoint, Google Drive, OneDrive, Outlook Contacts, Entra Directory, Google Contacts, Slack, Xero, HubSpot and Salesforce.

## What a label does not mean

* Experimental is not a separate plan and not an opt-in. No setting turns an experimental feature on or off.
* A label describes the feature, not your documents. A label never changes the status of a package or a template, and never changes what its audit trail records.