--- title: Share a dashboard description: Who can open a dashboard, what the canonical URL looks like, and how renaming keeps old links working with a redirect. updated: 2026-09-21 tier: free --- Every published dashboard has a URL you can send to someone. Whoever you send it to has to be able to sign in to an account that may see it. ## The URL Every dashboard lives in a workspace, at `https://.dashies.ai/`. A workspace slug is one you choose when you create the workspace. Your **handle** is derived from your email address when your account is created, **there is no way to change it**, and it does not appear in dashboard URLs. Slugs are lower-case letters, digits, and hyphens, up to 64 characters. Five slugs collide with the app's own paths on every subdomain, so do not use them: `pricing`, `auth`, `app`, `assets`, and `api`. `docs`, `privacy`, and `terms` are **not** reserved. You can name a dashboard `docs`. The older form `https://dashies.ai//` still works and redirects to the subdomain, keeping any query string. ## Who can open it There is no visibility setting. Every dashboard is access-gated, and the gate is the workspace it lives in: **any current member of that workspace** can open it, shown in the app as **Members**, and nobody else can. **There are no public dashboards.** A signed-out visitor is redirected to sign in with a return path, so after signing in they land on the dashboard they clicked - provided their account may see it. :::danger{title="Members only, with no exceptions"} There is **no share link, no per-viewer grant, and no anyone-with-the-link mode**. If you need someone else to see a dashboard, invite them to its workspace. This is the single most common wrong assumption about Dashies. A signed-in person who is not a member does not get an access-denied page: they get a 404 that is byte-for-byte identical to a URL that never existed, reading `This dashboard is private or no longer available.` That is deliberate, so a URL cannot be probed to discover whether a dashboard exists. ::: None of this is plan-gated: the gate is the same on every plan, including free. ## Renaming, and why old links keep working Renaming a dashboard is `update_dashboard` with a new slug. Ask your AI for it in plain language: > Rename my "q3-revenue" dashboard to "revenue-q3", keeping the display name > "Q3 Revenue". The old slug is kept as an alias, and the old URL **redirects** to the new one. Anyone holding the old link still lands on the dashboard. :::warning{title="A rename resets the display name unless you say otherwise"} Renaming without also passing a name sets the display name to the title-cased slug. If your dashboard is called `Q3 Revenue` and you rename the slug to `revenue-q3`, the name silently becomes `Revenue Q3`. Pass the name explicitly, as in the example above, to keep it. ::: Two refusals you may hit when reusing an old name: ```bash slug "revenue-q3" is already in use by another dashboard slug "revenue-q3" is already an alias for another dashboard ``` Aliases share the namespace with live slugs, so a name freed by a previous rename is not actually free. The redirect from an old link fires only after we have confirmed you may see the dashboard, which is why an old link bounces you through sign-in first. ## Link previews **A dashboard link does not unfurl** in Slack, X, or Discord. An unfurl is an unauthenticated preview - the crawler holds no session - and there is no reader for whom that would be correct, so nothing is revealed to a crawler at all. ## The Dashies badge No **Powered by Dashies** badge is added to a published dashboard, on any plan. Every dashboard is a members-only workspace dashboard, and that serve never adds one. See [what is gated](/concepts/plans-and-gating#what-is-gated) for what the plans do differ on. ## What a shared dashboard cannot do Published dashboards run in a sandbox on their own isolated origin. That is what stops one person's published page from reading another viewer's session. The consequence for you as an author: **a dashboard cannot use `localStorage`, cookies, or same-origin authenticated fetch**, and it cannot make network calls. See [what a viewer's browser can and cannot do](/concepts/dashboard-file#what-a-viewers-browser-can-and-cannot-do). Everything it needs must be in the file. See [Brand and design a dashboard](/guides/brand-a-dashboard) for how to embed fonts and logos under that constraint. ## Check it worked 1. **Open the URL in a private browsing window**, signed out. You should get the sign-in page, with the dashboard's URL carried through so you land back on it after signing in. That is correct, not a broken link. 2. **After a rename, open the old URL.** It should land on the new one. 3. **Check the display name** on [dashies.ai/app/files](https://dashies.ai/app/files) after any rename. If it changed and you did not want it to, republish the name. 4. **To confirm what a colleague will see**, ask them to open it, or use a browser profile that is signed into their account. Your own view tells you nothing about theirs, because you are a member.