> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/share/public-link.md).

# Your public link

Understand the public URL of a dForms form: what each part of /{account code}/f/{slug} means, where to copy it, how to change its last part with Edit link, and why links you already shared keep workin

Every form you publish gets one public address. Anyone with that address can open the form: no account, no login, no app.

***

## The shape of the URL

```
https://app.dforms.ai/{account code}/f/{form slug}
```

For example: `https://app.dforms.ai/acme/f/lead-qualification-quiz`

| Part             | What it is                                                                                                                                                  |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Account code** | A six character code for your workspace, for example `acme`. Dapta generates it for you.                                                                    |
| **f**            | A fixed segment, the same for every form. Everyone in the workspace copies the same link, and the link never names the person who built or shared the form. |
| **Form slug**    | The form itself, built from the form name (see below). You can change it with **Edit link**.                                                                |

You can see your account code under **Account settings** in the **Public page** tab: it is the end of the address of [your workspace page](/dforms/share/public-page.md), `app.dforms.ai/{account code}`. Your handle is not part of a form link.

***

**Step 1:** Open the form in the editor and click the **Copy link** icon (the chain link) in the topbar. The icon flashes a check mark and the full URL is on your clipboard.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-87c17c868d3006d7adf4b2a62641518cbdcc4684%2Fforms-public-link-01-copy-link.png?alt=media" alt="The editor topbar with the Copy link icon highlighted, followed by the Edit link, Embed, QR code and Open form icons"><figcaption><p><strong>Copy link</strong> in the editor topbar. Next to it sit <strong>Edit link</strong>, <strong>Embed</strong>, <strong>QR code</strong> and <strong>Open form</strong>, which opens the live form in a new tab.</p></figcaption></figure>

***

**Step 2:** You do not have to open the editor at all. On the **Forms** page, every row shows the public path under the form name, and carries the same **Copy link** and **Open form** icons on the right.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-ee42ea99dc30f82bef777b1ac6f83451e630cd36%2Fforms-public-link-02-forms-list-row.png?alt=media" alt="A row on the Forms page with the public path /acme/f/lead-qualification-quiz highlighted under the form name"><figcaption><p>The public path is printed right on the row, so you can read the URL without opening anything.</p></figcaption></figure>

***

**Step 3:** You also have one link of your own: the page at your handle that lists the forms of your workspace. Once that page is turned on, **Home** shows it in a box at the top with **Copy** and **Open**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-3a460f839954c830e45cbf4a66ef2407853e364f%2Fforms-public-link-03-home-card.png?alt=media" alt="The Home page with the workspace page box highlighted, showing app.dforms.ai/acme with Copy and Open"><figcaption><p>The workspace page box only appears while that page is published. See <a href="/dforms/share/public-page.md">Your workspace page</a>.</p></figcaption></figure>

***

## How the slug is made

When you create a form, dForms builds the slug from the name you typed:

* everything becomes lowercase,
* accents are removed, so `Cotización` becomes `cotizacion`,
* spaces and punctuation become single hyphens,
* it is cut at 60 characters,
* if another form in your workspace already uses that slug, or used it before its link was edited, a number is added: `contact-form`, then `contact-form-2`, then `contact-form-3`.

So a form named `Lead qualification quiz` gets the slug `lead-qualification-quiz`.

Renaming a form in the editor changes its name in your Forms list, never its link. To change the link itself, use **Edit link**.

***

## Edit the link

**Step 1:** In the editor topbar, click **Edit link** (the pencil next to **Copy link**). The dialog **Edit this form’s link** opens with the current slug. The start of the address, `app.dforms.ai/{account code}/f/`, is shown but cannot be changed: it belongs to your workspace, not to the form.

**Step 2:** Type the new ending in **Link** and click **Save link**. The button stays disabled until the value is valid and different from the current one.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f7e164fbd21cbe19534af15365f0619e583cfe95%2Fforms-public-link-04-edit-link.png?alt=media" alt="The Edit this form’s link dialog with the fixed app.dforms.ai/acme/f/ prefix, the Link field set to demo-request, and the Cancel and Save link buttons"><figcaption><p>Only the ending is yours to change. The dialog reminds you that links you already shared keep working.</p></figcaption></figure>

The new link works at once. It does not wait for **Publish**, and **Copy link**, **Embed**, **QR code**, **Open form** and the address bar of the preview switch to it straight away.

| Rule              | Detail                                                                                                                                          |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Characters        | Lowercase letters, numbers and single hyphens, with no hyphen at the start or the end. Capital letters are turned into lowercase when you save. |
| Length            | Up to 80 characters.                                                                                                                            |
| One form per link | No other form in the workspace may use it, now or before. A form can take back one of its own old links.                                        |

When something is off, the dialog says so under the field: *Use lowercase letters, numbers and hyphens, up to 80 characters.*, *That link is too long. Keep it under 80 characters.* or *Another form in this workspace is already using that link.*

***

## Vanity slug

The account code is short but not memorable. A **vanity slug** replaces it with a word you choose, so `app.dforms.ai/acme/f/demo` can read `app.dforms.ai/acme/f/demo`.

The vanity slug is a perk of a paid Dapta subscription, not a setting inside Forms. Ask your Dapta contact to set one up for your account.

Vanity slugs are lowercase letters, numbers and single hyphens, and a short list of words is reserved (`admin`, `api`, `login`, `pricing` and similar) because they are already used by the product itself.

***

## Old links keep working

Links you have already sent out do not break:

* **After Edit link**, the previous address keeps opening the form. Visitors are sent to the new link with everything after the `?` kept (UTM parameters, `embed=1`, prefill values), so printed QR codes, sent emails and embeds on other sites keep working.
* **Older links with a handle** in the middle, such as `app.dforms.ai/acme/alex/lead-qualification-quiz`, were handed out before links used the fixed `f`. They still open the form, with no redirect, and tell search engines that the `/f/` address is the main one.
* When your workspace gets a vanity slug, the old six character code keeps resolving to the same forms, for good. A link printed on a flyer last year still opens.
* The same is true if a vanity slug is ever replaced: the previous one keeps working too.

> **⚠️ Note:** Analytics triggers that match the page path, in Google Tag Manager or Google Analytics, need the current address. A trigger written for an older path with a handle only fires for visitors who use that old link, and one written for a slug you changed with **Edit link** stops firing. See [Tracking & pixels](/dforms/connect/tracking-and-pixels.md#page-paths-in-your-triggers).

Nothing about your link expires, and there is no way to close a form other than deleting it.

> **⚠️ Note:** Deleting a form deletes its submissions with it and turns its link, and every older link it had, into a not found page. Those addresses become free again, so a form you create or edit later can take them. There is no "unpublish" switch.

***

## What's next

* [Share with a QR code](/dforms/share/qr-code.md): the same link as a code for print and screens.
* [Embed on your website](/dforms/share/embed.md): show the same form inside your own page instead of linking out to it.
* [Your workspace page](/dforms/share/public-page.md): one address with your logo, your forms, your links and your social profiles.
* [Share card (social preview image)](/dforms/design/share-card.md): control the picture that appears when the link is pasted into a chat.
* [Hidden fields & URL prefill](/dforms/builder/hidden-fields-and-url-prefill.md): add `?key=value` to the link to fill answers in advance.


---

# 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.dapta.ai/dforms/share/public-link.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.