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

# Team Management

> Create teams, assign members and assistants, and manage team configuration in the Admin Panel Teams tab.

## What It Is

Team Management is the section of the Admin Panel where administrators organize users into named groups. It opens under **Admin Panel → Teams** and lists every team in the workspace as a card, with quick access to members and team configuration.

Teams are how PANTA OS reflects organizational structure inside the workspace. A user can belong to one team or several. Assistants can be assigned to specific teams through the Admin Panel, which determines who sees them in the Dashboard grid.

<Frame>
  <img src="https://mintcdn.com/panta/7med5cXzbjoQe_Qx/images/English-Images-Documentations-5.png?fit=max&auto=format&n=7med5cXzbjoQe_Qx&q=85&s=9355bb4b426a2395eeb06a7fb96c44b5" alt="English Images Documentations 5" width="1920" height="1080" data-path="images/English-Images-Documentations-5.png" />

  <img src="https://mintcdn.com/panta/7med5cXzbjoQe_Qx/images/English-Images-Documentations-5.png?fit=max&auto=format&n=7med5cXzbjoQe_Qx&q=85&s=9355bb4b426a2395eeb06a7fb96c44b5" alt="English Images Documentations 5" width="1920" height="1080" data-path="images/English-Images-Documentations-5.png" />
</Frame>

## Why It Matters

Teams give the workspace a structure that maps to how the organization already works.

<CardGroup cols={2}>
  <Card title="Organize members" icon="users">
    Group users by department, function, or project. A team makes membership explicit instead of relying on naming conventions.
  </Card>

  <Card title="Scope assistants to the right people" icon="bot">
    Assistants can be assigned to specific teams through the Admin Panel. Public assistants reach the teams they belong to; not every assistant has to be workspace wide.
  </Card>

  <Card title="Target Community posts" icon="megaphone">
    Posts created in the Community Feed can be sent to specific teams, so HR updates reach HR and Engineering changes reach Engineering.
  </Card>

  <Card title="Multi team membership" icon="layers">
    A user can belong to multiple teams at once. People who sit across functions do not need to be modeled as duplicates.
  </Card>
</CardGroup>

## How To Use It

<Steps>
  <Step title="Open the Admin Panel" icon="shield">
    Click Admin at the bottom of the sidebar. Visible to administrators only.
  </Step>

  <Step title="Open the Teams tab" icon="users">
    Switch to the Teams tab.
  </Step>

  <Step title="Scan the team list" icon="layout-grid">
    Each team appears as a card with its color icon, member count, name, and description. 
  </Step>

  <Step title="Open a team to edit it" icon="pen">
    Click a team card to open the team configuration in a modal. Four tabs organize the settings: General, Members, Assistants, Account actions.
  </Step>
</Steps>

## Creating a Team

<Steps>
  <Step title="Click Add Team" icon="plus">
    The button at the top right of the Team Management section opens the new team dialog.
  </Step>

  <Step title="Enter the team name" icon="tag">
    Team name is required. Use the same name your organization uses internally.
  </Step>

  <Step title="Upload a team image (optional)" icon="image">
    Upload team image accepts PNG or JPEG up to 2 MB. The image replaces the color icon on the team card. If you do this step, you will not select a team colour (below).
  </Step>

  <Step title="Pick a team color" icon="palette">
    Team color selects the icon color used when no image is uploaded. Five colors are available that are based on your company branding.
  </Step>

  <Step title="Add a description (optional)" icon="text-align-justify">
    Description is shown under the team name on the team card. Helps members and administrators understand the team's purpose at a glance.
  </Step>

  <Step title="Confirm" icon="check">
    Click Create team to create the team, or Cancel to discard the inputs. The new team appears as a card in the list.
  </Step>
</Steps>

## The Team Modal

Once a team is open, four tabs organize its configuration.

<CardGroup cols={2}>
  <Card title="General" icon="sticky-note">
    Basic team settings. Edit Team name, Description, Team image, and Team color. Save with Save changes.
  </Card>

  <Card title="Members" icon="users">
    Members of the team. Manage who belongs to the team here.
  </Card>

  <Card title="Assistants" icon="bot">
    Assistants assigned to the team. Once an assistant is made public by its creator, administrators can assign it here to specific teams.
  </Card>

  <Card title="Account actions" icon="alert-triangle">
    Critical team operations. Includes Delete team, which permanently removes the team. The action is irreversible; the dialog warns "Once you delete a team, there is no going back."
  </Card>
</CardGroup>

## Key Settings or Options

<CardGroup cols={2}>
  <Card title="Team name" icon="tag">
    The display name of the team. Editable later under General.
  </Card>

  <Card title="Team image and Team color" icon="image">
    Visual identifier for the team card. PNG or JPEG up to 2 MB, or one of five preset colors.
  </Card>

  <Card title="Description" icon="text-cursor">
    Optional short description shown on the team card.
  </Card>

  <Card title="Members" icon="users">
    Managed in the Members tab of the team modal. Each user can belong to multiple teams.
  </Card>

  <Card title="Assigned assistants" icon="bot">
    Managed in the Assistants tab of the team modal. Public assistants can be assigned to one or more teams.
  </Card>

  <Card title="Team deletion" icon="trash">
    In the Account actions tab. Permanent and irreversible; use carefully.
  </Card>
</CardGroup>

## Tips and Best Practices

* Mirror the organizational structure. Map teams to the units your organization already uses; do not invent new structures just for the platform.
* Use the description field. A short line under the team name saves administrators from guessing what the team is for.
* Assign assistants deliberately. A specialized HR assistant in the HR team is more useful than the same assistant exposed to the whole workspace.
* Keep team membership current. Teams that include former members make it harder to scope content correctly.
* Be deliberate about deletion. The Account actions tab makes the irreversibility explicit; a deletion mistake cannot be undone.

<Tip>
  Roles in PANTA OS are workspace wide (Admin or User), not team specific. There is no "team admin" or "team owner" tier. Membership in a team does not change a user's role.
</Tip>

## Help Center

<AccordionGroup>
  <Accordion title="Where is team management" icon="map-pin">
    Open Admin Panel from the bottom of the sidebar, then switch to the Teams tab.
  </Accordion>

  <Accordion title="Can a user be in more than one team" icon="layers">
    Yes. A user can belong to multiple teams at the same time. People who work across functions do not need duplicate accounts.
  </Accordion>

  <Accordion title="Is there a team admin role" icon="user">
    No. PANTA OS has two roles workspace wide: Admin and User. Membership in a team does not grant team specific administration rights; only workspace administrators manage teams.
  </Accordion>

  <Accordion title="How are assistants assigned to teams" icon="bot">
    Open the team and switch to the Assistants tab. Assistants made public by their creator can be assigned here. Private assistants stay with the user who created them.
  </Accordion>

  <Accordion title="Can I undo a team deletion" icon="rotate-ccw">
    No. Team deletion through the Account actions tab is permanent. The dialog warns about this before confirmation; once a team is deleted, it cannot be restored.
  </Accordion>

  <Accordion title="What happens to assistants assigned to a deleted team" icon="circle-question-mark">
    The assistants themselves are not deleted with the team; they remain visible to their creators. Only the team to team assignment is removed when the team is deleted.
  </Accordion>
</AccordionGroup>
