Skip to main content
Fork creates a new workspace from one document. It copies the current document and its referenced assets, but it does not copy comments or earlier version history.

​
Before you fork

You must sign in and have view access to the source document. You do not need edit access.

​
Fork the document

  1. Open the document and select Fork.
  2. If Workspaces asks you to sign in, select Log in, return to the document, and select Fork again.
  3. Enter the new workspace name.
  4. If destination choices appear, choose Personal or In organization. Workspaces uses Personal when no choices appear.
  5. Select Fork.
Workspaces opens the copied document in the new workspace.

​
What the new workspace contains

  • The current document content, including live edits that have not reached a save point, and its path.
  • Existing workspace assets linked from Markdown images or HTML src values that use paths relative to the document. Workspaces does not copy full web addresses, paths that start with /, or missing assets.
  • One new starting version.
The source document stays unchanged. Its comments and version history remain in the source workspace. A personal fork is private. An organization fork belongs to the selected organization and uses organization access. The person who forks the document becomes the new workspace owner.

​
If you cannot finish the fork

  • Sign in. Anonymous guests cannot finish a fork without an account.
  • Confirm that you can still view the source document.
  • If an organization is missing from the destination list, confirm that you are still a member of it.
  • If an organization fork is blocked because the organization is read-only, choose Personal.
  • If Fork reports an error, return to Home and check whether the new workspace exists before trying again. Workspaces can create the workspace and document before a linked asset fails to copy.
Read Add and organize files for path, move, conflict, and deletion rules in the new workspace. Reviewed July 20, 2026. Maintained by the Plannotator documentation team.
Last modified on July 24, 2026