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

# Teams

A **Team** in Avigrah defines **who can access and interact with an AI system**.

Teams act as the **access layer between users and projects**, ensuring that only the right users can view insights, trigger workflows, and interact with AI.

***

## What is a Team?

A Team is a **group of users assigned to one or more projects**.

Instead of giving users direct access to projects, Avigrah uses teams to:

* Control access centrally
* Group users by role or function
* Ensure consistent permissions across projects

***

## Teams as the Access Layer

Projects define the AI system.\
Teams define **who can use it**.

* Users are added to Teams
* Teams are assigned to Projects
* Access is granted through this relationship

This ensures:

> Users can only access AI outputs from the projects their team is assigned to.

***

## Who Belongs in a Team?

Teams are primarily designed for **AI Consumers**.

These are users who:

* Interact with AI through chat or UI
* Trigger tasks and workflows
* Consume insights and outputs

They do not manage pipelines, integrations, or system configuration.

***

## Role of Operators in Teams

Operators work at the **system level**, but also interact with teams when needed.

Operators can:

* Create teams
* Add or manage team members
* Assign teams to projects they manage
* Support AI consumers within teams

This typically applies to:

* Projects they have created
* Projects assigned to them by Admins

***

## Communication Flow

Teams also define how communication flows within the system.

* AI Consumers interact with AI
* If needed, they can raise requests or issues
* These are handled by Operators

This creates a structured flow:

**AI Consumer → AI System → Operator (if required)**

***

## Teams and Project Assignment

A single project can have **multiple teams**.

This allows:

* Different groups to access the same AI system
* Segmentation of users (e.g., Sales, Marketing, Leadership)
* Controlled visibility across teams

Each team only interacts with the project within its allowed scope.

***

## Why Teams Matter

### Controlled Access

Users only see what they are assigned to.

***

### Clean User Management

Manage access at the team level instead of individually.

***

### Scalable Collaboration

Easily support multiple teams across multiple projects.

***

### Clear Separation

System builders and AI consumers remain clearly separated.

***

## Future Enhancements

Avigrah is evolving Teams to support more advanced collaboration models.

Upcoming capabilities include:

### Team Context

AI responses can be scoped to the context of a specific team.

***

### Cross-Team Context

Controlled sharing of insights or signals across teams.

***

### Full Project Context

Option to enable broader visibility across the entire project when required.

***

These enhancements will allow more flexible collaboration while maintaining control and security.

***

## Best Practices

### Group Users by Function

Create teams based on roles such as Sales, Operations, or Management.

***

### Avoid Overlapping Access

Assign teams carefully to prevent unnecessary data exposure.

***

### Use Multiple Teams per Project

Segment users while still using the same AI system.

***

### Keep Teams Consumer-Focused

Avoid mixing system operators and AI consumers unnecessarily.