Aglet

How to triage confusion while switching workspaces

Workspace switching is a context problem first. Triage with synthetic memberships and similarly named workspaces, comparing the selected workspace, route, heading, and records shown. Keep a confusing label separate from a cross-workspace exposure or an action that creates work in the wrong tenant.

Establish what is happening

  1. Capture active context

    Record synthetic workspace names, membership roles, current route, page heading, selected switcher value, and the work item or project visible. Use names that differ clearly in the fixture while checking how similar names behave. Do not include customer records or session cookies.

  2. Exercise navigation paths

    Switch from the workspace home, open a project, follow a deep link, use back navigation, refresh, and open an old link. Compare route context and visible records after each transition. Keep a separate attempt for each workspace so cross-context leakage is easy to identify.

  3. Check action destination

    Create or edit only synthetic permitted work after switching and record which workspace receives it. Compare owner and restricted roles where supported. Mark a stale link, missing workspace, or unavailable membership as its own outcome rather than silently selecting a fallback.

What to carry forward

Triage is complete when the active workspace, route, membership, visible record scope, and action destination are known for each reproducible path. Elevate any cross-workspace record or write evidence immediately; a label-only ambiguity should retain its exact navigation trigger.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow