Workspaces Management
Workspaces organize docs across teams and products — belong to many, with a different role in each.
Workspace vs. project
This is the question we hear most, so here’s the quick mental model:
Workspace = the container
Your organization's home in Theneo. A workspace holds your projects, members, branding, and settings. Think of it as the company (or folder) everything else lives inside.
Project = one set of docs
A single body of documentation inside a workspace, usually one API or product. A single workspace can hold many projects.
So the hierarchy is simply Workspace → Projects → Sections. Keep one workspace with a project per API, or spin up separate workspaces per brand or team — whatever matches how your organization is structured.
“Project” and “documentation” mean the same thing. Across Theneo you’ll see both terms used for a single docs project — for example, “publish your documentation” and “publish your project” describe the exact same action.
Workspace basics
Your first workspace is created during sign-up as part of onboarding, and you’re assigned the Admin role in it.
You can also be invited to other workspaces by teammates or other organizations, and have different roles in each (for example, Admin in one and Editor in another). Your access always depends on the role you hold in that specific workspace.
Personal vs. Corporate
When creating a workspace, you choose a type:
- Personal — for individual or freelance use.
- Corporate — recommended for team collaboration.
Our recommendation: go Corporate
We strongly recommend a Corporate workspace, even when starting out. Corporate workspaces unlock team-oriented capabilities:
- Collaborating with team members in the same workspace
- Inviting members to workspaces and projects
- Working together within a project
- Sharing private projects with teammates
- Domain whitelisting and other company features
These are restricted in Personal workspaces.
Both Personal and Corporate workspaces are available on the Free tier. We only recommend Personal for specific individual-only use cases.
Switching Personal → Corporate (one-way)
You can upgrade a workspace from Personal → Corporate in the Admin configuration. Important: this change is permanent — there’s no step back, and you can’t switch Corporate → Personal.
Viewing your workspaces
From the dashboard, open the Workspaces page to see all workspaces you belong to, your role in each, and available actions (such as Leave).
Create an additional workspace
Create more workspaces anytime — useful for separating docs by team, product, client, or environment.
- Open the Workspaces page.
- Click + Create Workspace next to the page title.
- Complete the form: Name (required), Slug (auto-generated, editable), and Type (Personal or Corporate).
- Click Create.
The new workspace appears immediately, and you’re assigned the Admin role in it.
Leave a workspace
To tidy up workspaces you no longer need:
- Open the Workspaces page.
- Find the workspace you want to leave.
- Click Leave on the right of its row.
The workspace disappears from your list immediately.
Set a default workspace
Choose one workspace as your default — the starting point for key workflows:
- New projects are created in your default workspace (unless you choose another during the Create Project flow).
- Branding loads your default workspace’s settings first.
- Developer Portal configuration loads your default workspace first.
Switch workspace context
Even though Branding and the Developer Portal load from your default workspace, you can switch anytime — open Branding (or Developer Portal configuration) and use the workspace dropdown to select another workspace. The page updates to show that workspace’s settings.
Roles and permissions
Your role is set per workspace, so you can be an Admin in one and an Editor in another. These are the workspace roles:
Admin
Admin
Full control of the workspace: manage settings, members and their roles, branding, billing, publishing rights, and security (2FA, SSO, domain whitelisting), plus every project in the workspace.
Publisher
Publisher
Everything an Editor can do, plus publishing documentation live. By default, Admin and Publisher are the roles allowed to publish.
Editor
Editor
Create and edit content in the projects they can access. Editors do not manage workspace settings, and cannot publish unless publishing rights are extended to them.
Guest (Viewer)
Guest (Viewer)
Read-only access. Guests can view the projects shared with them but cannot edit or publish.
Workspace settings (Admin)
Admins manage the workspace from the Admin area, opened from the workspace dropdown. The Workspace Settings tab gathers the controls below, alongside User Management, External Customer Management, Audit Log, and Webhooks.
Details
Details
Edit the workspace name and slug, and see its type. The name and slug are editable; the type (Personal or Corporate) is shown here.
Documentation publishing rights
Documentation publishing rights
Choose which roles can publish documentation live. By default this is Admin and Publisher. See the Documentation Publishing Rights section for details.
Two-factor authentication
Two-factor authentication
Require every member to verify their identity with two-factor authentication before accessing the workspace. See the Two-Factor Authentication section.
Require SSO sign-in
Require SSO sign-in
Require members to sign in through SSO. When enabled, password sign-in is blocked for eligible users. See the SSO-Only Authentication Enforcement section.
Domain whitelisting
Domain whitelisting
Let anyone with your verified company email domain join the workspace automatically, at a permission level you choose (for example, guest). See the Whitelisting a Domain section.
FAQ
Can I create a project in a non-default workspace?
Can I create a project in a non-default workspace?
Yes. The default workspace is preselected, but you can choose a different one during the Create Project flow.
Why choose Corporate if I'm on the Free tier?
Why choose Corporate if I'm on the Free tier?
Because Corporate unlocks collaboration and company features — inviting members, sharing private projects, domain whitelisting — and it's included in the Free tier. Personal is best only for individual-only use cases.
If I leave a workspace, what happens to my access?
If I leave a workspace, what happens to my access?
Leaving removes your workspace-level access, not your project membership. You won't be able to create projects there or change its Branding/Developer Portal config, but you don't automatically lose access to projects you're part of — you'd only lose a project if removed from it separately.
Why do Branding and Developer Portal load from the default workspace?
Why do Branding and Developer Portal load from the default workspace?
It provides a consistent "home" context and reduces switching for users who mainly manage one workspace. You can still switch anytime via the dropdown.
On this page
- Workspaces Management