How organizations and workspaces work
The tenancy model behind every agent: organization → workspace → agent, isolated at every layer.
NeoXam Agents scopes everything along a three-level hierarchy. The organization is the billing root and the only place where sharing across teams happens. Workspaces belong to an organization and map to a team, product, or stage (for example dev and prod) — they are the default ownership boundary for agents, tools, credentials, and vaults. Agents live in exactly one workspace.
Sharing across workspaces
Nothing crosses a workspace boundary by accident. A resource is visible to other workspaces only when it is explicitly published at organization scope — for example a shared skill used by every agent in the company.
Isolation is enforced in the database
Tenant context is resolved from the verified token on every call and enforced as row-level security on every table — no cross-tenant query path exists by construction. Credentials are scoped per workspace in vaults, and rate limits and quotas apply per tenant. In production, client deployments run strict per-tenant workspaces.
Still stuck?
Tell us what you were trying to do and where it failed — screenshots and run IDs help. A human follows up.