> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravan.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations and roles

> Understand how Agni organizations, admins, and users work together.

An organization is the main workspace for your Agni account. It contains your agents, Campaigns (inbound and outbound), phone numbers, knowledge bases, integrations, billing, and team members.

Think of the organization as the business account. Admins manage the account, and users work inside it.

***

## What is an organization?

An organization is the top-level container for everything your team builds in Agni.

Each organization can have its own:

* Agents
* Campaigns (Inbound and Outbound)
* Knowledge bases
* Contacts
* Phone numbers
* Integrations
* Billing and credits
* Team members

The first person who creates the account becomes the initial admin for that organization.

<Note>
  Admins can create and manage organizations from their account when their plan or account access supports multiple organizations.
</Note>

***

## Admin role

Admins control the organization and its team access. This role is best for owners, managers, or technical leads who need full workspace control.

Admins can:

* Manage organization settings
* Invite users
* Add another admin
* Create and manage agents
* Manage Campaigns (Inbound and Outbound)
* Create and manage knowledge bases
* Manage integrations
* View usage and analytics
* Manage billing and credits

<Tip>
  Use the admin role for people who should be able to manage the workspace, not only operate inside it.
</Tip>

***

## User role

Users are team members who work inside an organization. This role is best for employees or operators who need to build and manage workflows without controlling the full account.

Users can usually:

* Create and update agents
* Manage Campaigns (Inbound and Outbound)
* Create and manage knowledge bases
* Work with contacts
* Review calls and performance data

Users have restricted access to account-level controls. For example, users cannot buy credits, invite new users, or add another admin.

<Warning>
  Exact permissions can vary by workspace configuration. If a user cannot access a feature, ask an admin to review their role and organization access.
</Warning>

***

## Role comparison

| Capability                              | Admin | User    |
| --------------------------------------- | ----- | ------- |
| Manage organization settings            | Yes   | Limited |
| Invite team members                     | Yes   | No      |
| Add another admin                       | Yes   | No      |
| Create agents                           | Yes   | Yes     |
| Manage Campaigns (Inbound and Outbound) | Yes   | Yes     |
| Create knowledge bases                  | Yes   | Yes     |
| Buy credits                             | Yes   | No      |
| Manage billing                          | Yes   | No      |

***

## When to use each role

Use **Admin** for people who manage the business account, billing, team access, and organization settings.

Use **User** for employees who need to build agents, run outbound workflows, manage inbound routing, or maintain knowledge bases without changing billing or team permissions.

***

## Next steps

<CardGroup cols={2}>
  <Card title="Workspace settings" icon="gear" href="/guides/settings">
    Manage organization settings, profile details, API keys, and team access.
  </Card>

  <Card title="Create an agent" icon="robot" href="/guides/create-first-agent">
    Build your first agent inside your organization.
  </Card>
</CardGroup>