Organizations and Workspaces

Recall organizes your work in two scopes: organizations and workspaces. Both have their own URL slugs, and every dashboard URL is built from the pair: /<orgSlug>/<workspaceSlug>/....

Concepts

Organization

The top-level container. Owns billing, members, plan tier, and one or more workspaces. Addressed by an immutable URL slug.

Workspace

A project scope inside an org. Holds workflows, chats, knowledge bases, tables, files, and scheduled tasks. Also slug-addressed.

When you sign up, Recall automatically creates a personal organization for you and a default workspace inside it. You don't have to choose a name or pick a plan — your first authenticated visit to / is enough.

Your personal org is a real organization with the Free plan applied. You can rename it later, invite teammates, and upgrade it to a paid plan — all the same controls that team-created orgs have. The only difference is that the slug was generated for you (e.g. mild-owl, prime-horse) instead of derived from a name you typed.

You'll know you've landed on it when the URL looks like:

https://app.tryrecall.com/<your-personal-org-slug>/<workspace-slug>/home

You can create additional organizations at any time from the workspace switcher — for example, when you start a paid team and want a clean billing scope.

URL Anatomy

Every dashboard URL is composed of two slug segments after the host:

https://app.tryrecall.com/<orgSlug>/<workspaceSlug>/...

Segment	Source	Mutable?
`<orgSlug>`	Generated from the organization name on creation, or a curated word-pair for personal orgs	Editable in Settings → Subscription (renaming an org breaks old links to that org)
`<workspaceSlug>`	A 6-character random slug generated when the workspace is created (e.g. `yxc35g`)	Immutable — display names live in the workspace `name` field and can be freely renamed without breaking URLs

Both slugs are unique within their parent scope:

Org slug: globally unique across the platform
Workspace slug: unique within an organization (so the same yxc35g could exist under two different org slugs)

When you rename an organization, the slug changes too. Old bookmarks and external links that pointed at the old slug will return a 404. Avoid renaming production orgs without coordinating with anyone who has bookmarks.

Switching Organizations and Workspaces

Use the workspace switcher at the top of the sidebar to move between scopes:

Switch workspace — Click the workspace name. A dropdown lists every workspace you have access to in the current organization. Picking one navigates to /<orgSlug>/<newWorkspaceSlug>/home.
Switch organization — In the same dropdown, click the organization name at the top. Recall lists every org you're a member of. Picking one navigates to that org's first workspace.
Create new workspace — At the bottom of the dropdown. Adds a workspace inside the current organization.
Invite members — Below "Create new workspace". Sends an invitation scoped to the current organization.

Upgrading from Personal to Team

When you upgrade your personal organization to a paid plan, Recall first prompts you to choose an organization name. The auto-generated word-pair slug works for solo use but is awkward to share with a team — the prompt is your chance to pick something readable.

The flow:

From Settings → Subscription, click Upgrade on the Pro or Max plan
The Organization Name dialog opens with your current name pre-filled
As you type, Recall checks slug availability in real time and shows a green check or a red conflict
Confirm to rename the org and continue to checkout

Renaming during this flow updates both the display name and the URL slug. If you'd rather keep the original slug — for example, because you've already shared links — leave the field unchanged and click confirm. The slug only changes when you actually edit the name.

API and Slug Considerations

User-facing dashboard URLs use slugs: /<orgSlug>/<workspaceSlug>/...
Admin and execution APIs use UUIDs (e.g. workspaceId query parameters in /api/v1/logs). The internal IDs are stable across renames, while slugs can change. See API Reference for details.
Webhooks and integrations stored on a workflow are addressed by the workflow's UUID, not by the workspace slug — they continue to work after a slug rename.

FAQ

Common Questions

You can't. The bootstrap is mandatory: every account must belong to at least one organization, and the personal org is the fallback. If you upgrade to a paid team org and want to leave the personal one behind, you can rename it or simply ignore it — but you can't delete the only org that contains you.

Not currently from the UI. Workspaces are created inside an organization and stay there. If you need to consolidate workspaces under a different org, contact support — we can migrate the underlying records, but external integrations bound to the old workspace ID will need to be re-pointed.

A two-word combo like `mild-owl`, `prime-horse`, or `quiet-river`, drawn from a curated word-pair list to avoid offensive or confusing combinations. Slugs are globally unique — if your generated pair is taken, Recall regenerates until it finds a free one.

No. Workspace slugs are 6-character random strings generated at creation time and are immutable. The display name is freely editable in Settings → Workspace, and the rename only affects what shows in the sidebar and switcher — the URL slug stays stable.

Recall generates short random slugs to keep URLs short, avoid name collisions across workspaces in the same org, and keep the URL stable across renames. If you'd prefer a memorable URL, the org slug (which IS derived from the name) carries that signal — `acme-corp/yxc35g/...` reads as 'Acme Corp's first workspace' once you know the convention.

API keys are scoped to a single workspace. To run executions in two workspaces (whether or not they share an org), you'll need separate keys. See Recall Keys in workspace settings to manage them.

Create a fresh organization for the team rather than renaming the personal one. From the workspace switcher click the org name at the top, then **Create new organization**. You'll be prompted for a name and slug, and the new org starts on the Free plan ready to be upgraded.