> 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-webcard-urls.md).

# Share WebCard URLs

WebCard URLs are public web-vCard pages for saved signatures.

## Availability

WebCard pages require Business.

## Copy a WebCard URL

1. Open **Signatures**.
2. Find the signature.
3. Open the action menu.
4. Click **Copy WebCard URL**.
5. Send or publish the copied URL.

## URL Format

WebCard URLs use a public slug based on the company and person name, for example:

```
https://your-domain.com/company-name/person-name
```

If a signature does not have a slug yet, Subscripta creates one when the WebCard URL is copied or when a Business user saves a QR-enabled signature.

## Notes

* The WebCard uses the saved signature profile details.
* Account-level WebCard branding is managed in **WebCard** settings.
* WebCard clicks can appear in Analytics as a WebCard source.


---

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