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

# Groups Management

> Organize users, track group spending, and manage collective access to API keys and features

Groups in Requesty allow administrators to organize organization members into logical units, track spending collectively, and manage user access efficiently.

<Note>
  **[Manage groups](https://app.requesty.ai/groups)** in the Requesty Console.
</Note>

## Groups System Overview

Groups provide a powerful way to organize your organization's users and manage their access to Requesty's features and API keys.

### What Groups Do

<CardGroup cols={2}>
  <Card title="User Organization" icon="users">
    Organize organization members into logical units like Marketing, Engineering, Sales, etc.
  </Card>

  <Card title="Spending Tracking" icon="chart-bar">
    Track monthly spending per group with aggregated spend monitoring
  </Card>

  <Card title="Access Management" icon="key">
    Allow admins to manage user access to API keys and features collectively
  </Card>

  <Card title="Team Structure" icon="sitemap">
    Reflect your company's organizational structure in your Requesty setup
  </Card>
</CardGroup>

## How Groups Work

### Creating Groups

Administrators can create named groups that match your organizational structure:

* **Department Groups**: Engineering, Marketing, Sales, Support
* **Project Groups**: Product A Team, Research Division, Beta Testers
* **Function Groups**: Admins, Developers, Content Creators
* **Custom Groups**: Any logical grouping that fits your needs

### Member Management

**Adding Members:**

* **Drag & Drop**: Intuitive interface for moving users between groups
* **Dialog-Based**: Select multiple users and assign to groups
* **Bulk Operations**: Add many users to groups simultaneously

**Removing Members:**

* Easy removal of users from groups
* View group membership at a glance
* Track who belongs to which groups

### Spending Tracking

Groups provide powerful spending insights:

* **Monthly Aggregation**: See total spending across all group members
* **Trend Analysis**: Track spending patterns over time
* **Budget Management**: Set and monitor group-level spending goals
* **Cost Allocation**: Understand which teams drive API usage

## Group Structure & Organization

### Hierarchical Organization

```mermaid theme={"dark"}
graph TD
    A[Organization] --> B[Engineering Group]
    A --> C[Marketing Group]
    A --> D[Sales Group]

    B --> E[Backend Engineers]
    B --> F[Frontend Engineers]
    B --> G[DevOps Engineers]

    C --> H[Content Team]
    C --> I[Design Team]

    D --> J[Sales Reps]
    D --> K[Sales Engineers]
```

### Flexible Membership

* Users can belong to multiple groups
* Cross-functional team support
* Project-based temporary groups
* Role-based permanent groups

## Integration with Features & API Keys

### Access Control Flow

<Steps>
  <Step title="Create Groups">Organize users into logical groups (Engineering, Marketing, etc.)</Step>
  <Step title="Configure API Keys">Create API keys with specific features and policies</Step>
  <Step title="Assign Access">Associate API keys with groups to grant access</Step>
  <Step title="Monitor Usage">Track group spending and feature usage</Step>
</Steps>

### API Key → Group Relationship

**How It Works:**

* API Keys can be associated with specific groups
* Groups determine which users can access which keys
* Features on API keys apply to all group members
* Policies control model access and behavior for the group

**Example Configuration:**

```yaml theme={"dark"}
Engineering Group:
  - API Key: 'eng-prod-key'
  - Features: [streaming, structured-outputs, reasoning]
  - Models: [gpt-4, claude-3]
  - Members: [alice@company.com, bob@company.com]

Marketing Group:
  - API Key: 'marketing-key'
  - Features: [prompt-library, auto-caching]
  - Models: [gpt-3.5-turbo]
  - Members: [carol@company.com, dave@company.com]
```

## Admin Panel Workflow

### Complete Group Management Process

<Tabs>
  <Tab title="Setup Phase">
    **Initial Configuration:** 1. Create groups for different teams/departments 2. Add organization members to appropriate groups 3.
    Configure API keys with specific features and policies 4. Set group-level spending monitoring
  </Tab>

  <Tab title="Daily Operations">
    **Ongoing Management:**: Monitor group spending and usage through analytics - Add new users to existing groups - Adjust API key
    features based on group needs - Track which groups are most active
  </Tab>

  <Tab title="Optimization">
    **Performance Tuning:**: Analyze spending patterns per group - Optimize feature assignments - Adjust group structures as teams evolve -
    Review and update access controls
  </Tab>
</Tabs>

## Key Relationships

Understanding how groups fit into the broader Requesty ecosystem:

### System Architecture

* **Groups** = User Organization (who can access what)
* **Features** = API Key Enhancement (how keys behave)
* **Policies** = Model Access Control (which models, fallbacks, load balancing)
* **Users** = Individual organization members with spending limits

### Integration Points

**Groups ↔ Users:**

* Groups contain multiple users
* Users can belong to multiple groups
* Group membership determines API access

**Groups ↔ API Keys:**

* API keys can be assigned to groups
* All group members can use assigned keys
* Features on keys apply to all group users

**Groups ↔ Spending:**

* Group spending is aggregation of member spending
* Useful for departmental budget tracking
* Helps identify high-usage teams

## Best Practices

<AccordionGroup>
  <Accordion title="Group Organization Strategy">
    **Recommended Approaches:**

    * Align groups with your actual team structure
    * Create both permanent (department) and temporary (project) groups
    * Use descriptive names that make sense to all admins
    * Plan for growth - create scalable group structures
  </Accordion>

  {' '}

  <Accordion title="Access Management">
    **Security & Control:**: Regularly review group memberships - Remove users from groups when they change roles - Use principle of least
    privilege for API key assignments - Monitor group spending to detect unusual usage
  </Accordion>

  <Accordion title="Spending Monitoring">
    **Cost Control:**

    * Set realistic spending expectations per group
    * Monitor trends to predict future usage
    * Use group data to allocate budgets appropriately
    * Identify opportunities for feature optimization
  </Accordion>
</AccordionGroup>

<Note>
  Groups provide fine-grained control where admins can organize users logically while configuring sophisticated API key behaviors through
  features and policies.
</Note>

## Advanced Features

### Analytics & Reporting

* Group spending trends over time
* Feature usage by group
* Model preference analysis per group
* Cost efficiency metrics

### Automation Options

* Auto-assign new users to default groups
* Spending alerts at group level
* Usage-based group recommendations
* Integration with external team management tools

The groups system enables sophisticated organization management while maintaining simplicity for day-to-day operations.