> 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-page.md). # Your workspace page (link in bio) Publish one page for your whole workspace at app.dforms.ai/{account code}: your logo, a short bio, the forms and links you choose in your order, and your social profiles. Share it as a link in bio or Your workspace page is one link that holds everything you want people to reach: your logo, your name, a short bio, buttons to the forms and links you pick, and icons for your social profiles. Think of it as a link in bio page, built from your own forms and dressed in your brand kit. It lives at the address of your workspace: ``` https://app.dforms.ai/{account code} ``` For example `https://app.dforms.ai/acme`. There is one page per workspace, and anyone in the workspace can edit it. The page is off until someone publishes it: until then the address is a not found page. **Good uses for it:** * **Trade fairs and events.** Print the QR code on a card, a banner or an NFC card at your booth. Visitors scan it and pick the form they need: book a demo, join the list, enter the raffle. * **Your Instagram or TikTok bio.** Social profiles allow a single link. Put this one there and list every form and page you want behind it. * **One link for all your forms.** Hand out one address in your email signature or your WhatsApp profile instead of one link per form. *** ## Open the editor **Step 1:** Click your name at the bottom of the left menu to open the account menu, then choose **Public page** under **Account settings**.

The page is edited from Account settings, Public page.

You land on **Your workspace page**. The editor is on the left and a **Preview** of the page, in a phone sized frame, is on the right. The preview is drawn by the same code as the public page, so it shows exactly what visitors will get, and it updates as you type.

Your workspace page in Account settings, with the Published switch and the row with the page address, Copy link, QR code and Open highlighted, and the Preview on the right — The **Published** switch, and your page address with **Copy link**, **QR code** and **Open**.

> **💡 Note:** The page belongs to the workspace, not to you. If you work in several workspaces, switch to the right one first: each workspace has its own page at its own account code. *** ## Set up the header **Step 2:** Choose the picture at the top of the page under **Photo or logo**. | Option | What it does | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Use brand kit logo** | The default. The page shows the logo of your [brand kit](/dforms/design/brand-kit.md). If the brand kit has no logo, your initials show instead. | | **Upload image** | Pick a PNG, JPEG, WebP or GIF from your computer. It is cropped to a square and resized for you. | | **No logo** | Shows the initials of the page name instead of a picture. | | **Or paste an image link** | Use an image that is already online. The link must start with `https://`. | The same picture is used on the link preview when someone shares your page in a chat or on social media. **Step 3:** Fill in **Name** and **Bio**. * **Name** is the title of the page. Left empty, the page uses the name of your workspace. * **Bio** is one or two lines under the name, up to 280 characters.

Photo or logo, Name and Bio make up the top of the page.

*** ## Add your buttons **Step 4:** Under **Buttons**, build the list of buttons the page shows. Forms and links live in the same list, so you can mix them in any order. * **Add a form** opens a list of the forms in your workspace. Pick one and it is added at the end. Each form can be added once, and its button shows the form's public title. * **Add a link** adds a row with a **Label** (the text on the button, for example *Our website*) and a **URL**, which must start with `https://`. * The arrows on the left of each row (**Move up**, **Move down**) change the order. The page shows the buttons top to bottom in this same order. * The trash icon (**Remove**) takes a button off the page. Removing a form button does not touch the form. A page holds up to 30 buttons.

The Buttons list with three forms and two links, the Move up and Move down arrows of one row highlighted, and the Add a form and Add a link controls highlighted below the list — Forms and links in one ordered list. Use the arrows to reorder and the controls below to add more.

On the page, a form button opens the form in the same tab. A link button opens in a new tab. > **⚠️ Note:** If a form on the page is deleted, its button drops off the page by itself. The page never shows a broken button, and there is nothing to clean up. *** ## Add your social profiles **Step 5:** Under **Social links**, fill in the networks you use: **Instagram**, **X**, **YouTube**, **TikTok** and **WhatsApp**. Only the ones you fill in show on the page, as a row of icons under your bio, and each opens in a new tab. * For **Instagram**, **X**, **YouTube** and **TikTok**, paste your profile link (`instagram.com/yourbrand`) or just your handle (`@yourbrand`). When you leave the field, it turns into the full link that will be saved. * For **WhatsApp**, type your phone number **with the country code**, starting with `+`, for example `+57 300 123 4567`. Visitors who tap the icon open a WhatsApp chat with that number (a `wa.me` link). No WhatsApp Business setup is needed.

The Social links section with Instagram, X, YouTube, TikTok and WhatsApp fields, and the WhatsApp field highlighted with its hint Visitors open a WhatsApp chat with this number — Leave a network empty and its icon does not show. WhatsApp takes a phone number with its country code.

> **💡 Tip:** If a value is not recognized, the field turns red and tells you what it expects, for example *Add the country code at the start, with a +, like +57 300 123 4567.* *** ## Publish and share **Step 6:** Click **Save**. The message **Page saved.** confirms it. **Step 7:** Turn the **Published** switch on (top right). The switch saves the page too. From now on the address is live, and an **Open** link next to **QR code** takes you to it. To take the page down, turn **Published** off. Visitors get a page not found again, and everything you set up is kept for when you turn it back on. **Step 8:** Share it. The row under the title gives you three ways: * **Copy link** puts `app.dforms.ai/{account code}` on your clipboard. * **QR code** opens a QR code for the page with **Download SVG** and **Download PNG**. Use the SVG for print: it stays sharp at any size. * **Open** shows the live page in a new tab.

The QR code for your page dialog with the QR code, the page address and the Download SVG and Download PNG buttons highlighted — Scanning the code opens your workspace page. Print it on cards, banners or your booth.

While the page is published, **Home** also shows its link at the top, with **Copy** and **Open**, so it is always at hand. *** ## What visitors see The page uses your [brand kit](/dforms/design/brand-kit.md): its colors, typeface, corner style and button style, the same way your forms do. A visitor who moves from the page into a form does not feel a jump.

The live page: logo, name and bio, then your social icons and your buttons, in the order you set.

Most visitors arrive from a phone, so the page is built for it first: one column of large buttons that fits a small screen, whether the page has one button or many.

The same workspace page on a phone, with the social icons highlighted, the buttons in one column and the Made with dForms badge at the bottom — The same page on a phone.

* The fixed words on the page (such as the badge at the bottom) follow the visitor's browser language. Add `?lang=en` or `?lang=es` to the link to force one. Your name, bio and button labels show exactly as you wrote them. * When the page is shared in a chat or on social media, the preview card shows your picture, your name and your bio. ### The Made with dForms badge At the bottom of the page sits the **Made with dForms** badge (**Hecho con dForms** in Spanish), the same one your forms carry. It opens the dForms website in a new tab.

The bottom of the workspace page with the Made with dForms badge highlighted under the last button — The badge sits under the last button.

*** ## Links you shared before Before the workspace page existed, each member could publish a personal page at `app.dforms.ai/{account code}/{handle}`. Those addresses still work: they now take visitors straight to the workspace page. Form links (`app.dforms.ai/{account code}/f/{form slug}`) are not affected. *** ## What's next * [Share with a QR code](/dforms/share/qr-code.md): a QR code for a single form instead of the whole page. * [Your public link](/dforms/share/public-link.md): the address of a single form, and how the slug is built. * [Brand kit](/dforms/design/brand-kit.md): the logo, colors and typeface the page borrows. * [Public page settings](/dforms/account/public-page-and-identity.md): where this page sits among the account settings. --- # 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-page.md?ask=&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.