> 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/complete-walkthrough.md).

# Complete walkthrough

This guide takes a new user from account creation to a deployed signature.

## 1. Create Your Account

1. Open Subscripta.
2. Choose **Sign Up**.
3. Create your account with email and password, or continue with Google, LinkedIn, or Microsoft.
4. If you use email and password, confirm your email if the app asks you to.
5. Accept the Terms of Service and Privacy Policy by completing signup.
6. Optionally choose whether to receive newsletters and product updates.

After signup, Subscripta sends new users to the setup flow.

## 2. Complete Setup

1. Enter your full name.
2. Enter your company or business name.
3. Select your team size.
4. Click **Get started**.

These details are used for your account profile and help organize the workspace.

## 3. Create Departments

Departments help you organize signatures by team, role, or business unit.

1. Open **Departments**.
2. Click **New Department**.
3. Enter a department name, such as Sales, Marketing, HR, Support, or Engineering.
4. Click **Create**.

Free and trial accounts can create up to 2 departments. Pro and Business include unlimited departments.

## 4. Choose a Template

1. Open **Templates**.
2. Browse the template gallery.
3. Hover a template and click **Use this template**.
4. The builder opens with that template selected.

You can also start directly from **Builder** and choose a template inside the form.

## 5. Build the Signature

1. Fill in the employee's full name and email.
2. Add job title, department, phone, website, and company name.
3. Add social links if needed.
4. Upload or paste URLs for a profile photo, company logo, or campaign banner.
5. Choose brand colors and font.
6. Enable QR code if the signature should include a scannable vCard.
7. Review the live preview.

Required fields are full name and email. Other fields are optional and can be left blank.

## 6. Save the Signature

1. Click **Save Signature** in the builder.
2. The signature is stored in your account.
3. You can find it later under **Signatures**.

Saved signatures can be edited, duplicated, shared, copied as HTML, or deleted.

## 7. Export and Install

1. Use **Gmail / Outlook** for direct paste into Gmail or Outlook.
2. Use **HTML -> Copy HTML** for webmail or source-based install flows.
3. Use **HTML -> Email Clients** for desktop clients such as eM Client that rewrite advanced CSS.
4. Use **Download -> PNG** or **Download -> JPG** only when exact visual appearance matters more than links.
5. Use **Apple Mail** for the guided Apple Mail setup.
6. Use **Plain Text** as a fallback for systems that reject HTML.

After installing, send a fresh test email to the clients your team cares about.

## 8. Share With an Employee

1. Open **Signatures**.
2. Open the action menu for a signature.
3. Click **Share**.
4. Send the copied `/share/...` URL to the employee.

The share page lets the employee preview and export the signature without signing in. It does not let the employee save edits back to your account.

## 9. Track Performance

Analytics are available on Pro and Business.

1. Open **Analytics**.
2. Review total clicks, active signatures, top link type, top performer, clicks by link type, clicks by source, top signatures, and recent activity.
3. Use the 7-day or 30-day filters on Pro.
4. Use **All time** on Business.

Analytics appear after recipients click tracked links in deployed saved signatures.

## 10. Manage Your Plan

1. Open the user menu.
2. Click **Subscription**.
3. Review your current plan, signature slot usage, renewal or trial status, and feature comparison.
4. Upgrade or manage billing as needed.


---

# 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/getting-started/complete-walkthrough.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.