Skip to main content
Your Home can show personal and organization workspaces. A personal workspace has no organization and has one owner. A workspace you create while signed in or fork to Personal starts private. A claimed anonymous workspace keeps its current sharing setting. An organization workspace belongs to one organization, has one owner, and normally starts with access for every organization member. Hosted Workspaces calls an organization a team in buttons, tabs, and messages.

Compare personal and organization workspaces

The owner can rename or delete the workspace and change its sharing settings. An organization admin does not gain those owner controls unless Workspaces reassigns the workspace to them when a member leaves.

Find an organization workspace

On hosted Workspaces:
  1. Open Home.
  2. Under Your organizations, select the organization. Workspaces labels each organization row Shared home.
  3. Select Workspaces. The page lists workspaces under Shared with [organization name].
The organization page shows organization workspaces that you own or that are set to Your organization, Anyone with the link can view, or Anyone with the link can view and edit. A guest link does not make a workspace appear in this list. Another member’s private workspace stays hidden here, even if a separate guest link lets you open it.
Your workspaces on Home contains every workspace you own and every workspace set to Your organization from the organizations loaded into your current session. If another owner changes an organization workspace to Anyone with the link can view or Anyone with the link can view and edit, that workspace may disappear from your Home list. Open the organization’s shared home to find it.
A hosted browser session loads up to 20 organization memberships. If your account belongs to more organizations, some shared homes and their workspaces may not appear in that session. The 20-organization browser-session cap does not apply to API keys. An API key loads up to the first 100 current organization memberships.

Create a personal workspace

The browser’s New workspace action always creates a personal workspace.
1

Open the workspace form

From Home, select New workspace under Your workspaces.
2

Name the workspace

Enter an optional name, then select Create workspace. An empty name creates an Untitled workspace.
Workspaces opens the new workspace. It starts private to you, even when your account belongs to an organization.

Create an organization workspace

The browser cannot create an empty workspace directly in an organization or move an existing personal workspace into one. You can create an organization workspace in either of these ways:
  • Fork a document, then choose the organization as the destination. The fork creates one new organization workspace with new history.
  • Use the Workspaces API to create a workspace with the organization’s org_id. See Use the Workspaces API.
Fork each document separately if you use the browser. Each fork creates its own workspace. There is no browser action that moves the whole personal workspace or transfers its history.
Do not use Share and Your organization to move a personal workspace. The browser currently offers that choice when your account belongs to an organization, but Workspaces rejects it because the workspace does not yet belong to that organization. Create and organize a workspace lists the current alternatives.

Understand ownership and member access

An organization workspace still has one owner. By default, every organization member can view and edit it, while the owner keeps the workspace-management controls. Admin and Member roles grant the same workspace access. The owner can later make the workspace private or share it more widely. Guest links give access separately from the workspace setting. See Who can view or edit a workspace before changing access. When an admin removes a member, Workspaces gives the member’s organization workspaces to that admin, including any organization workspaces the member kept private. Personal workspaces and workspaces in other organizations do not move. When a member leaves on their own, Workspaces gives those organization workspaces to the remaining admin who joined first. Review the steps in Invite and remove organization members.

After an organization trial ends

After a trial ends, organization workspaces become read-only when Workspaces reports the organization as expired. Workspaces keeps write access active when the organization’s subscription status or billing exemption allows it. People who still have access can keep reading documents, comments, versions, and artifacts. Workspaces blocks changes to content and workspace settings, but owners can still list and revoke existing guest links. Personal workspaces remain editable. What happens when a trial ends lists the allowed and blocked actions.

Self-hosted Workspaces

A self-hosted instance has one configured organization. Every signed-in person joins that organization as a member. The identity provider controls who can sign in. Self-hosted Workspaces shows one Your workspaces list. The current Home may also show an empty Your organizations heading, but it does not show a team row to open. The hosted Members and Settings team pages are unavailable. The New workspace action still creates a personal, private workspace. An organization workspace appears in Your workspaces when your organization membership grants access. Reviewed July 22, 2026. Maintained by the Plannotator documentation team.
Last modified on July 24, 2026