Skip to main content
A workspace is where decks, files, members, invitations and the audit log live. Everything you do in Slideless happens in exactly one workspace at a time, and nothing crosses from one workspace to another: a deck, a file, a member list or an audit row belongs to one workspace and is invisible from every other, even on the same instance and even to that instance’s other owners.

​
One person, several workspaces

An account is a person, not a seat in one workspace. The same sign-in can belong to several workspaces, with a different role in each: owner of your own, plain member of a client’s. The workspace switcher in the sidebar lists them. For the API, the CLI and agents, the workspace is a per-request choice: send X-Workspace-Id: <workspace id>, or leave it out to land in your default workspace. GET /api/v1/me lists the workspaces you can name and the one the request resolved to. Being a member of a workspace is not a grant on its decks. Inside a workspace, a deck is readable by its owner, by the workspace’s admins and owners, and by the collaborators invited on it (Decks).

​
A workspace holds projects

A workspace can be split into projects (Projects): a name, a description, members taken from the workspace’s own roster, and the decks linked to the project. A project is the way to give a few colleagues one client’s decks without opening the rest. Any member creates one and becomes its manager; the workspace’s admins and owners act as managers on every project. On cloud the workspace roster is managed at Antasphere, but its projects stay in Slideless.

​
Creating another workspace

The first workspace of a self-hosted instance is created at setup. After that, a signed-in person creates another one from the workspace switcher, and becomes its owner. It starts empty: no deck, no member and no audit row is carried over, and the workspace you were in is not told. In the dashboard, open the workspace menu at the top of the sidebar and choose New workspace. Give it a name; once it is created the dashboard switches to it, so you land in the new workspace. The menu is there as soon as you may create a workspace, even if you belong to only one. When creation is closed and you belong to one workspace, the sidebar shows the instance name and no menu. Someone who is signed in but belongs to no workspace yet is offered the same dialog on the page that says so. Files you download from the dashboard (deck attachments, files sent through a form, exports) always come from the workspace you are in.
The name is 1 to 120 characters; surrounding spaces are trimmed. Pass the returned id as X-Workspace-Id to work in the new workspace. The call accepts an Idempotency-Key header, so a retried request never creates two. Who can create one:
  • A browser session only. API keys, OAuth tokens and MCP agents are refused: creating a workspace is a person’s decision, never a credential’s.
  • Not a guest. Someone whose only access is a per-deck collaborator invitation cannot (403 guest_forbidden). A member of any workspace can, whatever their role there.
  • Within the operator’s limit. On a self-hosted instance one person can own up to MAX_WORKSPACES_PER_USER workspaces (10 by default); past it the call answers 403 workspace_limit_reached. With the variable at 0, creation is closed for everyone (403 workspace_creation_disabled). See Deployment profiles.
GET /api/v1/me carries canCreateWorkspace, true when the call would be accepted right now. A client shows or hides its “new workspace” entry from that one flag. On cloud the flag stays true for someone who signed in before workspace creation existed: their first attempt answers 401 hub_reauth_required, they sign in again, and the retry goes through.

​
On Slideless cloud

On cloud a workspace is an Antasphere organization (Antasphere account). Creating a workspace from Slideless creates the organization at Antasphere, in your name, with you as its owner, and it appears in Slideless at once. The number of organizations one person can own is Antasphere’s limit. Members of that organization are then invited and managed at account.antasphere.com, like every other organization.

​
Leaving and deleting

A workspace must keep at least one active owner, so the last owner cannot leave, be demoted or delete their account while they are the only one. An account that belongs to several workspaces cannot be deleted by an admin of one of them: that admin deactivates the membership instead, and the account stays with its other workspaces.