Guide

When to separate agents by identity vs workspace

Use identities for hard operational boundaries and shared workspaces for collaboration across those boundaries.

Updated 2026-03-12

AnonyStack dark-mode dashboard screenshot

Problem

Teams often ask whether a new workflow should become a new identity or just another shared workspace. The wrong choice usually creates either unnecessary coupling or unnecessary fragmentation.

Short workflow

  1. Ask whether the new workflow needs its own inbox, tokens, or sensitive app state.
  2. If yes, create a new identity.
  3. If the workflow mainly needs collaboration across existing identities, create or use a shared workspace.
  4. Link the planning work back to the relevant identities instead of collapsing them together.

Choose a new identity when

  • It needs a separate mailbox
  • It needs its own API token boundary
  • It should be removable without affecting other workflows
  • It owns distinct operational state

Choose a shared workspace when

  • Several identities need the same planning board
  • The main need is coordination, not a new inbox
  • Operators need a collaborative layer across existing identities

Default rule

Use identities for separation and workspaces for collaboration. If you are unsure, start with a new identity first.