> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/admin/teams.md).

# Teams

**Teams** let you organize people by area so you can track each team's engagement and set specific usage permissions.

Follow the steps below to create teams, add members, and set permissions.

### Create a team <a href="#create-a-team" id="create-a-team"></a>

To create a new team, follow these steps:

1. At the top of the page, click **+ Create team**.
2. In the **Team name** field, enter the team name.
3. Optionally, fill in the **Description** field.
4. Click **Save**.

### Find a team <a href="#find-a-team" id="find-a-team"></a>

In the **Teams** tab, enter a name in the **Search teams** field. The list shows each team's name and description, number of **Users**, and total **Interactions**.

### Add users to a team <a href="#add-users-to-a-team" id="add-users-to-a-team"></a>

To add users who aren't on a team yet, follow these steps:

1. Click the **Users without a team** tab.
2. Select the checkbox next to each user. To select every user on the page, select the checkbox in the list header.
3. Click **Add to team**.
4. In the **Select a team** field, choose the team.
5. Click **Add to team** to confirm.

{% hint style="info" %}
The number of selected users appears above the list (e.g., **25 selected**).
{% endhint %}

### Edit a team <a href="#edit-a-team" id="edit-a-team"></a>

To edit a team, follow these steps:

1. In the **Teams** tab, click **Edit** next to the team.
2. Make your changes in the **General**, **Members**, or **Usage permissions** tabs.
3. Click **Save**.

### Set usage permissions <a href="#set-usage-permissions" id="set-usage-permissions"></a>

In the **Usage permissions** tab, you define what team members can do with each Astro feature. For each action, choose one of these options:

* **Inherit:** keeps the default permission from the user's profile. This option is selected by default.
* **Allow:** enables the action for team members.
* **Deny:** blocks the action for team members.

{% hint style="info" %}
**Important:** when a person belongs to more than one team, their teams' permissions are combined. If any one of their teams allows an action, it's enabled for that person.
{% endhint %}

Permissions are organized by the following features:

* **Experts (agents):** use, create, share, and share publicly.
* **Skills:** use, create, share, and share publicly.
* **Schedules:** use and create.
* **Prompts:** use, create, and share.
* **Memories:** use, create, update, read, and opt out.
* **File search:** use.
* **File citations:** use.
* **MCP servers:** use, create, share, share publicly, and configure on-behalf-of.
* **Web search:** use.
* **Code execution:** use.

### Delete a team <a href="#delete-a-team" id="delete-a-team"></a>

To delete a team, follow these steps:

1. In the **Teams** tab, click **Edit** next to the team.
2. Click **Delete team**.
3. Confirm the action in the confirmation dialog.

{% hint style="warning" %}
This action can't be undone once confirmed.
{% endhint %}

See also: [Users](https://docs.skyone.cloud/english/admin/users.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.skyone.cloud/english/admin/teams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
