Workspace

Projects

Create, open, rename, duplicate, and organize projects in your workspace.

Projects is your home workspace: a list of projects you can open, filter, and manage. Each project has a root diagram and may contain nested child diagrams.

What you see

Each project card typically shows:

  • Name
  • Updated time
  • Ownership / team context (when relevant)
  • Actions menu

Filters commonly include personal, shared, team, templates, and trash. Use search when the list grows large.

Create a project

  1. Click New project.
  2. Optionally pick a template.
  3. Open the editor and start building.

Empty projects are fine — you can flesh them out later or replace content via import.

Open a project

Click the card (or Open) to enter the editor on the root diagram. Nested child diagrams open from inside a parent node (see Nested diagrams).

Rename

From the project card menu choose Rename, enter a new title, and confirm. Renaming does not change IDs used in exports or public share URLs for nested paths.

Duplicate

Duplicate creates a copy of the project’s diagram tree so you can experiment without touching the original.

Use cases:

  • Branch a production architecture sketch for a redesign
  • Fork a template into a client-specific project
  • Keep a “draft” next to a “canonical” version

Save as template

Save as template stores the current project’s diagram tree as a reusable starter. Templates appear when creating new projects. See Templates.

Leave / ownership

If a project belongs to a team or was shared with you:

  • Leave removes your access without deleting the project for others.
  • Owners can transfer ownership to another user when available.

Deleting is different from leaving — see Trash.

Personal vs team projects

Personal projects stay yours until you share them. Team projects appear for members according to team membership — see Teams.

Tips

  • Name projects by system or domain (Payments platform, Staging network), not by date alone.
  • Duplicate before large refactors.
  • Export a JSON bundle before destructive experiments if you need an offline backup.