> ## 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.

> ## 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.

# Report a problem

> A bug report template, where to send a security vulnerability, and how to flag a mistake in these docs.

## Reporting a bug

Send bug reports to [support@flowsign.app](mailto:support@flowsign.app) or through the in-app form under **Account > Support** (see [Support](/guides/account/support)). Copy the template below into your message; a report with all five parts is usually fixed faster than one that needs a follow-up question.

```text theme={null}
What I was doing:
  (page or endpoint, and the package or template id if there is one)

What I expected:

What happened instead:
  (the exact error text, or a screenshot)

When:
  (date and time, with your time zone)

How often:
  (every time, sometimes, once)
```

For API problems add the request path, the status code and the error body, with the key and any webhook secret redacted. See [Contact support](/support/contact) for the full list.

## Reporting a security vulnerability

Do not send security issues to the general support address or raise them in a public place.

Email [security@flowsign.app](mailto:security@flowsign.app) with a description of the issue and steps to reproduce. Flowsign aims to acknowledge reports within one business day, keeps you updated as it investigates, and credits you once the issue is resolved if you would like credit. Please give the team a reasonable time to fix an issue before publishing it.

There is no bug bounty programme at present. The [Trust centre](https://flowsign.app/trust) describes the current disclosure process and what is on the security roadmap.

## Reporting a documentation error

If a page here is wrong, out of date or missing something, use the **Report a problem** link in the navigation bar at the top of every page. It opens an email to support with the subject already filled in; add the page address and what needs changing.