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

# FlowSign documentation

> Send documents for signature, build reusable templates, and drive FlowSign from your own systems with the REST API and webhooks.

FlowSign is a PDF e-signature platform for teams. Upload documents, add recipients, place fields, and send. Every package keeps an audit trail and produces a certificate of completion when the last recipient finishes.

FlowSign is a trading name of Studio Phoenix Limited (New Zealand). The app lives at [my.flowsign.app](https://my.flowsign.app); the product site is [flowsign.app](https://flowsign.app).

## Start here

<CardGroup cols={2}>
  <Card title="Getting started" icon="rocket" href="/getting-started">
    Create an account and send your first package.
  </Card>

  <Card title="Building a workflow" icon="workflow" href="/guides/building-a-workflow">
    Turn a document you send often into a template with roles, fields and reminders.
  </Card>

  <Card title="Developer quickstart" icon="code" href="/developers">
    Create an API key, instantiate a template and send a package from your own code.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/webhooks/overview">
    Get notified when packages are sent, opened, signed, declined, voided or expired.
  </Card>
</CardGroup>

## Concepts

| Term      | Meaning                                                                                                                                                                                                                                                   |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Package   | One send: a set of documents, the recipients who act on them, and the signing sessions that result. A package moves through `DRAFT` (or `SCHEDULED`, when it has a send time), `IN_PROGRESS` and `COMPLETED`, or ends as `DECLINED`, `VOID` or `ON_HOLD`. |
| Recipient | A person on a package. A **Signer** completes fields, a **Viewer** reads the package while it is out, and a **CC** recipient receives the finished copy by email.                                                                                         |
| Session   | One recipient's turn on a package. Sessions are created when the package is sent and are what webhooks report on.                                                                                                                                         |
| Template  | A reusable package definition: documents, named roles, fields, merge fields, email copy, reminder and expiry settings.                                                                                                                                    |
| Workspace | A division of your organisation (an office, region or team) with its own packages, templates, contacts and members.                                                                                                                                       |

## Need help?

Email [support@flowsign.app](mailto:support@flowsign.app).

Something on these pages wrong, out of date or missing? Tell us with **Report a problem** in the top bar and we will fix it.