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

# Groups

> Create and manage groups for efficient, bulk access control across indexes and agents.

Groups let you manage access for teams of users instead of assigning permissions one person at a time. When you share an index or agent with a group, every member of that group gets access.

## When to use groups

Groups are useful when:

* A team of people needs access to the same set of indexes and agents
* You frequently add or remove users who need the same permissions
* You want to manage access by department, role, or project rather than per individual

## Creating a group

<Steps>
  <Step title="Navigate to groups">
    Open your workspace settings and go to the groups section.
  </Step>

  <Step title="Create a new group">
    Give the group a descriptive name that reflects its purpose, for example, "Field Engineering Team" or "Sales - West Region."
  </Step>

  <Step title="Add members">
    Add users to the group by email. Users can belong to multiple groups.
  </Step>
</Steps>

## Assigning group access

Once a group exists, you can share indexes and agents with it:

* **Index access:** Go to the index settings and add the group as a Viewer or Admin
* **Agent access:** Go to the agent settings and add the group as a Viewer or Admin

All current and future members of the group inherit the assigned permissions.

## Managing group membership

When someone joins or leaves a team:

* **Adding a user to a group** immediately grants them access to everything shared with that group
* **Removing a user from a group** immediately revokes the group-based access (they keep any individually assigned permissions)

This makes onboarding and offboarding straightforward: add new hires to the right groups, and remove departing employees.

## Example setup

A typical workspace might use groups like:

| Group                 | Indexes shared                                  | Agents shared          |
| --------------------- | ----------------------------------------------- | ---------------------- |
| **Field Engineering** | Product Manuals, Troubleshooting Guides         | Field Support Agent    |
| **Sales Team**        | Product Catalogs, Pricing, Competitive Analysis | Sales Enablement Agent |
| **Support Reps**      | Knowledge Base, FAQs, Service Policies          | Customer Service Agent |
| **RFP Team**          | All technical docs, Compliance, Past Proposals  | RFP Agent              |

<Tip>
  Name groups by function, not by individual teams. "Field Engineering" is better than "John's Team." It stays meaningful as people change roles.
</Tip>