# Separate Organizations

Create separate organizations for different companies, clients, or departments with isolated data and independent billing.

Organizations let you run completely separate AI workforces under one account. Each organization has its own employees, teams, skills, data, billing, and settings. Nothing crosses the boundary. A marketing agency can create one organization per client, keeping each client's data, employees, and conversations fully isolated.

Switch between organizations instantly from the workspace. Your personal account holds your own AI employees. Each organization you create or join has a separate workforce. Members, roles, and permissions are managed per organization. Invite team members to specific organizations without giving them access to others.

Billing is per organization. Each one has its own credit balance, usage tracking, and subscription plan. This makes it straightforward to track costs per client, per department, or per project. No shared pool, no allocation guesswork.

## Separate Organizations for Every Client or Department

Organizations in Sistava provide complete isolation between distinct business units. Each organization has its own AI workforce, data, billing, and configuration. A marketing agency can run a separate org per client. An enterprise can run a separate org per department. Nothing crosses the boundary.

Isolation is not just logical. Storage, tool credentials, employee context, and activity logs are all scoped to the organization. A client's proprietary data never appears in another client's agent context. This is the foundation for deploying autonomous agents at scale without compliance risk.

## Multi-Tenancy Built Into the Platform, Not Bolted On

Most AI agent platforms are single-tenant by design, requiring workarounds for multi-client deployments. Sistava was built multi-tenant from the start. Every record in the platform is scoped to an organization. Every query is filtered by tenant. There is no shared state to accidentally leak.

For agencies, this means one Sistava account can serve every client with full separation. For enterprises, it means business units can operate independently while IT maintains a single platform. Multi-agent orchestration across organizations without the administrative burden of separate accounts.

## Billing and Permissions Scoped by Organization

Each organization has its own billing account, subscription, and usage tracking. Agencies can pass through costs to clients directly. Enterprises can allocate AI workforce spend by department. Credits used in one org do not affect another.

Role-based access control is also organization-scoped. An admin in one org has no visibility into another. Invite team members, set permissions, and manage access independently per organization. The right people see the right things, nothing more.

## Use Cases

### Agency managing AI employees for multiple clients

Create a separate organization for each client. Their AI agents, knowledge, and data stay fully isolated from one another.

### Holding company running multiple business units

Each business unit gets its own organization with independent AI employees, settings, and access controls.

### SaaS company offering AI workforce to customers

Provision a clean organization per customer. Every tenant operates in a fully isolated environment.

### Consulting firm protecting client confidentiality

Separate organizations ensure one client's AI agent never touches another client's data or workflows.

## Comparison

| Before | After |
|---|---|
| Running AI for multiple clients in one workspace creates data leakage risk. | Each organization is fully isolated, separate data, agents, and permissions. |
| Switching between client contexts is manual and error-prone. | Move between organizations instantly with clear separation at every layer. |
| Shared AI agents pick up context from the wrong client. | Agents belong to one organization and only see what belongs there. |
| Access control across multiple clients is complex to manage. | Permissions, members, and settings are scoped per organization. |

## FAQ

### Is data completely isolated between organizations?

Yes. Every piece of data in Sistava, including employee context, Drive files, task history, and tool credentials, is scoped to a single organization. There is no shared state between organizations.

### Can I manage multiple organizations from one account?

Yes. A single Sistava account can be a member of multiple organizations. You switch between them from the account menu. Each org has its own billing, AI workforce, and settings.

### Does each organization get separate billing?

Yes. Billing is per organization. Usage, credits, and subscription plans are tracked independently. This makes it straightforward to allocate costs to clients or departments.

### How many AI employees can one organization have?

The number of AI employees per organization depends on your plan. Each employee is an independent agent with its own context, tools, and task history within the organization.

### Can I run separate AI workforces for multiple clients or business units?

Yes. Each organization is fully isolated with its own employees, knowledge, settings, and billing. You can switch between organizations without any data crossing over.

> I manage AI employees for three separate clients from one account. Each client's data stays completely isolated. My clients love it and I stopped worrying about mixing things up.
> — James O., AI Automation Consultant · independent practice