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

# Overview

> Understanding teams and their implementation in the Thena platform

Teams in the Thena platform provide a structured way to organize members, manage workflows, and handle ticket routing within your organization. They serve as the primary unit for work distribution and collaboration.

<Note>
  Teams can be organized hierarchically, allowing for parent-child relationships that reflect your organizational structure. A member can belong to multiple teams, each with specific roles and responsibilities.
</Note>

## What is a team?

A team in Thena Platform represents a group of members who:

* Work together on specific projects or areas
* Share common workflows and processes
* Handle related tickets and tasks
* Have defined roles and permissions

## Team structure

### Team hierarchy

<CardGroup cols={2}>
  <Card title="Parent teams" icon="sitemap">
    • Department level teams <br />
    • Broad responsibility areas <br />
    • Cross-functional groups <br />
    • Regional divisions
  </Card>

  <Card title="Sub teams" icon="diagram-project">
    • Specialized units <br />
    • Project teams <br />
    • Product teams <br />
    • Support tiers
  </Card>
</CardGroup>

### Team types

<CardGroup cols={2}>
  <Card title="Public teams" icon="users">
    • Visible to all organization members <br />
    • Open for viewing and joining requests <br />
    • Transparent workflows
  </Card>

  <Card title="Private teams" icon="user-lock">
    • Limited visibility <br />
    • Invitation-only membership <br />
    • Protected resources
  </Card>
</CardGroup>

## Team settings

### Basic configuration

<AccordionGroup>
  <Accordion title="Team information" icon="info">
    * Team name and description
    * Team type (public/private)
    * Parent team association
    * Team icon and color
  </Accordion>

  <Accordion title="Access control" icon="shield">
    * Member roles and permissions
    * Resource access levels
    * Workflow permissions
    * Integration access
  </Accordion>

  <Accordion title="Routing rules" icon="route">
    * Ticket assignment logic
    * Load balancing settings
    * Priority handling
    * Escalation paths
  </Accordion>
</AccordionGroup>

### Member management

<CardGroup cols={2}>
  <Card title="Roles" icon="user-gear">
    • Team Admin: Full team control <br />
    • Team Lead: Operational management <br />
    • Member: Standard access <br />
    • Observer: Read-only access
  </Card>

  <Card title="Permissions" icon="key">
    • Ticket management <br />
    • Resource access <br />
    • Configuration rights <br />
    • Member management
  </Card>
</CardGroup>

## Best practices

<Steps>
  <Step title="Team setup">
    * Define clear team purpose
    * Establish team hierarchy
    * Set up access controls
    * Configure routing rules
  </Step>

  <Step title="Member management">
    * Define role responsibilities
    * Document access levels
    * Set up onboarding process
    * Maintain member roster
  </Step>

  <Step title="Operations">
    * Regular team reviews
    * Performance monitoring
    * Process documentation
    * Resource allocation
  </Step>
</Steps>

## API endpoints

### Sample team

```json theme={null}
{
  "name": "Customer Support",
  "description": "Primary support team handling customer inquiries",
  "type": "PUBLIC",
  "parentTeamId": "team-123",
  "icon": "https://example.com/icon.png",
  "color": "#FF5733"
}
```

<Note>
  When creating a team, the system will add additional fields in the response such as `uid`, `organizationId`, `createdAt`, `updatedAt`, `isActive`, and `memberCount`.
</Note>

### Available operations

<Accordion title="Team management" icon="users-gear">
  ```bash theme={null}
  # List all teams
  GET /v1/teams

  # Create team
  POST /v1/teams
  Content-Type: application/json

  # Get team by ID
  GET /v1/teams/{id}

  # Update team
  PATCH /v1/teams/{id}
  Content-Type: application/json

  # Delete team
  DELETE /v1/teams/{id}
  ```

  <Note>
    All endpoints require authentication. Include your API key in the Authorization header.
  </Note>

  For detailed API specifications, see <a href="/api-reference/platform/teams/create-a-team" target="_blank">Team Management</a>
</Accordion>

<Accordion title="Member operations" icon="users">
  ```bash theme={null}
  # List team members
  GET /v1/teams/{id}/members

  # Add team member
  POST /v1/teams/{id}/members
  Content-Type: application/json

  # Remove team member
  DELETE /v1/teams/{id}/members/{memberId}
  ```

  #### Add member request

  ```json theme={null}
  {
    "userId": "user-123",
    "role": "MEMBER"
  }
  ```

  For detailed API specifications, see:

  * <a href="/api-reference/platform/teams/add-a-team-member" target="_blank">Add Team Member</a>
  * <a href="/api-reference/platform/teams/get-all-team-members" target="_blank">List Team Members</a>
</Accordion>

<Accordion title="Team configuration" icon="gear">
  ```bash theme={null}
  # Get team configuration
  GET /v1/teams/{id}/configuration

  # Update team configuration
  PATCH /v1/teams/{id}/configuration
  Content-Type: application/json
  ```

  #### Configuration request

  ```json theme={null}
  {
    "workingHours": {
      "timezone": "America/New_York",
      "schedule": {
        "monday": [{"start": "09:00", "end": "17:00"}],
        "tuesday": [{"start": "09:00", "end": "17:00"}]
      }
    },
    "routingRules": {
      "assignmentStrategy": "ROUND_ROBIN",
      "priorityWeights": true
    }
  }
  ```

  For detailed API specifications, see <a href="/api-reference/platform/teams/update-team-configurations" target="_blank">Team Configuration</a>
</Accordion>

## Related resources

<CardGroup cols={2}>
  <Card title="Organizations" icon="building" href="/platform/core-concepts/organizations/overview">
    Learn about organization management
  </Card>

  <Card title="Routing" icon="route" href="/platform/core-concepts/teams/routing">
    Configure team routing rules
  </Card>

  <Card title="Tickets" icon="ticket" href="/platform/core-concepts/tickets/overview">
    Understand ticket management
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/platform/core-concepts/workflows/overview">
    Set up team workflows
  </Card>
</CardGroup>