Workspaces
A workspace is the operational boundary for agents, users, provider credentials, tools, traces, and API keys.
Most teams map one product environment or customer account to one workspace. Workspace membership controls who can configure agents, inspect sessions, manage provider keys, and review operational data.
What belongs to a workspace
Section titled “What belongs to a workspace”- Agents and their attached persona versions.
- Users and their conversation history.
- Provider credentials for model, speech, and voice vendors.
- Custom tools and webhook endpoints.
- API keys used by your backend services.
- Observability traces, feedback, audit logs, and test runs.
Tenant isolation
Section titled “Tenant isolation”Hyponema stores workspace data under a tenant boundary. Backend requests set tenant scope before database access, and row-level security prevents cross-tenant reads or writes.
Your integration should never send a workspace API key to the browser. Create sessions from your backend and pass only the signed session URL or token to client-side code.
Environments
Section titled “Environments”Use separate workspaces for production and test traffic when you need clean provider credentials, test users, trace history, and operational settings.