> For the complete documentation index, see [llms.txt](https://docs.subscripta.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subscripta.app/team-management/manage-team-signatures.md).

# Manage team signatures

The Signatures page lists all saved signatures in your account.

## What You Can Do

* Search signatures by name, email, or job title.
* Filter signatures by department.
* Create a new signature.
* Edit an existing signature.
* Duplicate a signature.
* Copy signature HTML.
* Share a signature export page.
* Copy a WebCard URL on Business.
* Delete a signature.

## Steps

1. Open **Signatures**.
2. Use search or department filters to find a signature.
3. Open the action menu for that row.
4. Choose the action you need.

## Plan Limits

| Plan     | Signature Slots |
| -------- | --------------- |
| Free     | 2               |
| Pro      | 50              |
| Business | 200             |

If you reach your slot limit, the app blocks new signature creation until you upgrade or delete unused signatures.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.subscripta.app/team-management/manage-team-signatures.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.