Workspaces and Teams

Synchronex supports personal work and shared team work without mixing tenant data. A personal scope holds the founder's baseline identity, products, and decisions. Team workspaces add shared context, invitations, member access, and workspace-level billing. Agency-style work can carry client-specific context when a workspace needs stricter boundaries.

Memory is layered by scope. The product spec defines personal, team, and agency scopes with explicit merge rules: narrow context can override scalar fields, while constraints accumulate across active scopes. This lets a team share operating memory while still preserving a user's private baseline and preventing cross-client leakage.

Every workspace-backed row is expected to remain tenant-isolated through user ownership, workspace identifiers, and Supabase row-level security. Invitations and workspace switching are UI conveniences over that isolation model, not a bypass around it.

Read the full guide →