Choose an organization
Understand how AgentStack resolves the active workspace after sign-in.
AgentStack uses the organization resolver after sign-in or when a link needs an active workspace. It loads the memberships available to the signed-in user, prefers a valid previously used organization slug from browser storage, and otherwise selects the first accessible organization. The selected slug is persisted for up to a year so the next visit can return to the same workspace.
OAuth outcomes are also routed through this resolver. A successful or failed provider callback is forwarded to the resolved workspace’s Integrations page so the person who initiated connection setup can see the result. If the resolver cannot load memberships, it exposes a retry path rather than guessing a workspace. When a user has no organization, it does not invent a create-organization state.
For support and deep-link design, link directly to a known /org/<slug>/… path whenever your system already knows the intended organization. Let /org/resolve handle interactive recovery, not authorization. The resolver selects a workspace for navigation; every destination still applies its own membership, role, and plan checks.