Workspaces
A workspace is the operating boundary for a Hyponema team. Agents, Users, knowledge, integrations, voices, provider credentials, API keys, observability data, settings, and billing all belong to a workspace.
What belongs to a workspace
Section titled “What belongs to a workspace”Workspace-scoped surfaces include:
- Agents and their attached knowledge, actions, distribution settings, tests, and privacy settings.
- Users, conversation history, calls, memory records, and observability traces.
- Knowledge sources, integrations, voice catalog state, provider credentials, and API keys.
- Members, SSO, privacy settings, compliance workflows, audit events, wallet credits, usage, and payment method.
Operator model
Section titled “Operator model”Clients operate the workspace through the dashboard. Members should have the minimum access needed for their role. Use Settings to manage members, API keys, provider credentials, privacy, compliance, and audit records.
Workspace isolation
Section titled “Workspace isolation”Hyponema treats workspace data as isolated. Public docs describe this at a product level: do not reuse API keys across customers, do not move User records between workspaces, and do not expose one workspace’s credentials or records to another.
Common setup issues
Section titled “Common setup issues”If a page appears empty or disabled, check:
- You selected the expected workspace.
- The workspace has the required member access.
- Provider credentials are present in Settings.
- Wallet credits are available and the relevant usage limit has not been reached.
- The surface is enabled for the workspace.