Teams
Teams provide a way to organize users inside a workspace.
Instead of assigning permissions and responsibilities to individual users one by one, organizations can group users into teams and manage access collectively.
Teams simplify collaboration and make workspace administration easier as organizations grow.
Why Teams Exist
Section titled “Why Teams Exist”As AI systems become larger, multiple groups of people are typically involved:
- Developers building AI systems
- Business users consuming AI services
- Managers approving requests
- Administrators governing the platform
Managing permissions individually quickly becomes difficult.
Teams provide a scalable way to manage users and responsibilities.
Common Team Structures
Section titled “Common Team Structures”Organizations commonly create teams based on departments or responsibilities.
Examples include:
Engineering
Section titled “Engineering”Responsible for:
- Building Agents
- Creating AI Flows
- Managing Skills
- Maintaining AI infrastructure
IT Operations
Section titled “IT Operations”Responsible for:
- Reviewing access requests
- Managing approvals
- Operating support workflows
Human Resources
Section titled “Human Resources”Responsible for:
- Employee onboarding
- Policy management
- HR approvals
Finance
Section titled “Finance”Responsible for:
- Budget approvals
- Expense reviews
- Financial workflows
Creating Teams
Section titled “Creating Teams”Teams can be created from:
Settings ↓Manage TeamsEach team contains:
- A team name
- A description
- A list of users
Team Configuration
Section titled “Team Configuration”Team Name
Section titled “Team Name”The display name of the team.
Examples:
EngineeringIT OperationsFinanceHuman ResourcesDescription
Section titled “Description”An optional description explaining the purpose and responsibilities of the team.
Example:
Responsible for managing internal IT systems and employee access requests.Users can be added to one or more teams.
Teams allow organizations to manage groups of users rather than assigning permissions individually.
Example:
Engineering Team├── Alice├── Bob└── CharlieTeams and Permissions
Section titled “Teams and Permissions”Teams themselves do not grant permissions.
Instead, teams are commonly used together with:
- RBAC
- Approvals
- Service Catalogs
This allows organizations to assign responsibilities at the team level rather than the individual level.
Teams and Approvals
Section titled “Teams and Approvals”Teams are often used as approval targets.
Examples:
- IT Team approves VPN access requests.
- Finance Team approves expenses.
- Security Team approves privileged access requests.
This allows workflows to continue operating even when individual users change roles or leave the organization.
Relationship to Other Concepts
Section titled “Relationship to Other Concepts”Users ↓Teams ↓RBAC ↓ApprovalsTeams provide the organizational structure that connects users with governance policies.
The Karyam Philosophy
Section titled “The Karyam Philosophy”AI systems are rarely operated by a single person.
Teams make collaboration, governance, and ownership scalable across the organization.
