> 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/getting-started/launch-checklist.md).

# Launch checklist

Use this checklist before deploying signatures across a team.

## Account

* [ ] Create your account.
* [ ] Complete setup.
* [ ] Confirm your company name is correct in **Settings**.
* [ ] Review your plan limits in **Subscription**.

## Organization

* [ ] Create departments for the main groups in your team.
* [ ] Decide which template or brand style should be the default.
* [ ] Upload public HTTPS versions of logos, profile photos, and banners.

## Signatures

* [ ] Create one test signature first.
* [ ] Add all required fields: full name, email, job title, department, company, phone, website, and social links.
* [ ] Add campaign banner and banner click URL if needed.
* [ ] Enable QR vCard if your plan includes it and your workflow needs it.
* [ ] Save the signature.

## Testing

* [ ] Send test emails from the real sender account.
* [ ] Test Gmail web, Gmail iPhone, Outlook, Apple Mail, and the desktop client your team uses.
* [ ] Test dark mode on Gmail iPhone if the design uses white text on dark backgrounds.
* [ ] Verify images load without being signed in to Subscripta.
* [ ] Verify links open the expected destination.

## Rollout

* [ ] Share the `/share/...` page with employees who need to install their own signatures.
* [ ] Give client-specific installation instructions.
* [ ] Use **Email Clients** export for eM Client or other desktop apps that rewrite advanced CSS.
* [ ] Use PNG or JPG only when appearance matters more than clickable links.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.subscripta.app/getting-started/launch-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.