Overview
Every Taskade Genesis surface lives at one of three URL shapes: /spaces, /d, and /flows. The diagram below also shows /user/{handle}, a related but non-Genesis shape that points to a creator's Community profile. Knowing which one to copy keeps your share links tight, your bookmarks accurate, and your customers landing on the right page the first time.
TL;DR: Apps live at
/spaces/{spaceId}, projects at/d/{projectId}, and automations at/flows/{flowId}. The Space is your Taskade Genesis app, so link to the Space when you want someone to use the deployed surface. See Publishing apps for share controls and access settings.
The three Genesis URL shapes (plus community profiles)
The first three rows are the canonical Taskade Genesis URL shapes, each mapped to one of the three Workspace DNA layers. The fourth row, /user/{handle}, is a related shape that points to a Community profile rather than a Genesis surface. Pick the URL that matches what you want the visitor to do.
| URL pattern | What it points to | Typical use |
|---|---|---|
/spaces/{spaceId} |
Your Taskade Genesis app, the published surface visitors land on | Share the live app, embed it, attach a custom domain |
/d/{projectId} |
A single Project (task tree, notes, or database) | Collaborate on tasks, hand off a single doc, link from chat |
/flows/{flowId} |
An Automation (trigger plus actions) | Wire up a webhook, share a workflow, schedule a run |
/user/{handle} |
A Community profile (related, non-Genesis shape) | Link to a creator's gallery and follow them |
Each pattern is stable. You can copy a Space URL today and trust it in next year's email campaign.
When to share which
Pick by intent, not by what is open in your browser tab.
- To let someone use your app, share the Space link. They land on the app shell, sign in if needed, and start using the live surface.
- To collaborate on tasks or notes inside one project, share the Project link. Teammates open the project directly, with whichever Project View you set as default.
- To let an external system trigger your workflow, share the Automation link with a webhook. The webhook URL belongs to the Automation, not the Space.
If you are not sure, start with the Space link. It contains everything else.
Custom domains and short links
Attach a custom domain to a Space and the domain becomes the canonical URL. Old /spaces/{spaceId} links still work as redirects, so you can roll out the new URL without breaking existing references. See Custom Domains for the full setup.
Short branded links (for example tk.app/launch) point at the same Space underneath. They read better in newsletters, slide decks, and conference QR codes.
Privacy and access
URL shape and access control are independent. Every link, regardless of pattern, respects the access settings on the underlying object.
- Workspace members are gated by the 7-tier permission model (Owner, Maintainer, Editor, Commenter, Collaborator, Participant, Viewer).
- End users of a published app are managed in App Users.
- Password protection and sign-in requirements are set per Space in Publishing apps.
- Public Apps featured in the Community Gallery use the same Space link as the private build.
A leaked URL still cannot be opened by someone who lacks permission. Trust the access controls, not URL secrecy.
Embed the right URL
Embedding follows the same rule. Use the Space URL when you want the full app inside an iframe, the Project URL when you only want a single task list or table, and the Automation URL when you want a status badge for a running Automation.