> 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/share-signatures-with-employees.md).

# Share signatures with employees

Use sharing when an employee needs to install their own signature without accessing your Subscripta account.

## Share the Export Page

1. Open **Signatures**.
2. Find the employee's signature.
3. Open the action menu.
4. Click **Share**.
5. Send the copied `/share/...` link to the employee.

The shared page lets the employee preview the signature and export it using Gmail / Outlook, HTML, image, or Apple Mail options.

## What the Share Page Does

* Shows the saved signature preview.
* Lets the recipient copy for Gmail / Outlook.
* Lets the recipient copy HTML.
* Lets the recipient download an email-client-safe HTML file.
* Lets the recipient download PNG or JPG.
* Lets the recipient open the Apple Mail install flow.

## What the Share Page Does Not Do

* It does not require the employee to sign in.
* It does not let the employee save changes to your database.
* It does not update the original signature record.
* It does not give account access.

## About Employee Edit Links

The current app has an internal owner edit URL in the format `/app/?id=SIGNATURE_ID`. That URL opens the saved signature in the authenticated Builder and saves changes to the account database.

Do not send the internal owner edit URL as a public employee link unless that employee should sign in to the account and edit the saved record.

If your workflow uses a separate client-side employee edit page, treat those edits as local to the employee's export session only. They should not be described as saved account changes unless the app explicitly writes them back to the database.


---

# 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/share-signatures-with-employees.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.