Organization Workspace

The organization workspace is the control room for everything shared across agents.

What Lives Here

Main organization pages include:

• Agents
• Team
• Shared Skills
• Integrations
• Usage
• Billing
• Organization Settings

Profile and Account Settings remain available from the global user menu because they belong to the signed-in operator, not the organization.

Agents

This is the post-login landing page for the organization.

It gives you:

• organization-wide stats
• a searchable agent fleet list
• recent activity
• date-range filtering
• agent creation for admins

Use this page when you need to switch context or compare agents before going deeper.

Duplicate an agent

Organization administrators can duplicate an agent from the fleet list. The new agent starts with a new identity in the same organization; the source agent stays unchanged. The dialog lets you include the knowledge base, skills, tools, MCP servers, interceptors, and eligible workspace artifacts.

The copy is intentionally a mix of independent and shared rows:

• copied agent configuration, ready sources' published documents/chunks, and eligible workspace artifact bytes become destination data; unpublished recrawl generations are excluded
• organization skills, tools, and shared media remain shared with the source, so later edits to those shared resources affect both agents
• API keys, voice-provider identifiers, MCP credentials, live runs, shares, and tool-operation history are not copied

After starting the operation, open the destination workspace to watch its copy status. For each warning or blocked source, use the recorded remediation rather than retrying blindly.

Workspace artifacts include generated outputs and user uploads, not knowledge-source uploads (those belong to the knowledge-base option). The report shows workspace-stage failures even when no knowledge sources were selected. Completed files remain available; inspect the reported failure and source/destination files before uploading missing files manually or starting a new duplication.

If the report shows AGENT_DUPLICATION_COPY_OUTCOME_UNKNOWN, do not retry the copy or delete its provider object manually. An administrator must confirm whether the storage-provider write completed before releasing reserved storage. There is no self-service reconciliation action in the dashboard.

Finish the new agent safely

1. Create new agent-scoped API keys before installing a widget or calling the public API. Existing widget and SDK keys remain scoped to the source agent.
2. If the agent uses voice, review its native voice defaults in Agent Settings, confirm deployment readiness, then choose devices and test a new session in Voice Lab. There is no remote sync step.
3. Re-enter MCP credentials and reconnect each copied MCP server. The duplicate preserves safe connection structure but begins credential-free and disconnected.
4. For a blocked source, fix the original source condition and explicitly re-ingest or re-index it from Sources. This is a new ingestion action and can consume the tenant's configured quota or spend; the duplication itself does not silently create that work.
5. Review shared skills, tools, and media before changing them. Make a separate shared-resource copy only when the new agent needs independent behavior.
6. Test the destination in Playground and on a staging widget installation before sending traffic to it.

Billing And Usage

Billing and Usage are organization-level because they span more than one agent.

• use Billing for plan management, hosted credit balance, top-ups, and auto-recharge
• use Usage for hosted-credit burn, BYOK activity, and workload analysis across the tenant

Shared Skills

Skills are organization-level reusable instructions. Create or install them in the organization workspace, then attach them to specific agents from the agent dashboard.

Integrations

Integrations contains organization-level MCP connections and MCP API keys. Agent-specific tools and MCP servers remain in the selected agent workspace.

Organization Settings

Organization Settings includes:

• branding
• team management
• provider keys for BYOK workflows

Best Practices

• treat provider keys as shared infrastructure, not agent-level experiments
• keep hosted-credit balance and auto-recharge ownership with the organization admins
• keep branding decisions separate from prompt or answer-quality work
• review the agent fleet regularly so unused or unhealthy agents do not drift unnoticed

First Admin Workflow

1. confirm billing ownership and who can manage hosted spend
2. add provider keys if your plan uses BYOK
3. create the first agent
4. add team members with the minimum role they need
5. hand the new agent off to the dashboard owner for source setup and testing

Related Docs

Organization Settings & Team

Manage branding, team access, and provider keys.

Usage & Costs

Understand where AI, voice, and ingestion spend is going.

Billing

Manage platform plans, hosted credits, top-ups, and auto-recharge.

Skills

Create reusable behavior and attach it to agents.

Getting Started

Use the fast path from first login to first launch.