> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/workspace-and-settings/teams.md).

# Teams

Teams group the members of your firm. A team decides two things for its members: which clients they see, and which sensitive actions they can take. Open **Settings → Access → Teams** to see them.

Every firm has an **Everyone** team. It is marked with a lock and every member belongs to it.

## Creating a team

Admins see **New team** on the Teams tab. Enter a name (for example "NY team") and click **Create team**. You become the team's first team admin.

On the team's page, click **Add members**, pick the people to add, and choose their team role:

| Team role      | What it allows                                                                                   |
| -------------- | ------------------------------------------------------------------------------------------------ |
| **Team admin** | Add and remove members of this team, change their team role, and grant the team client segments. |
| **Member**     | Belongs to the team and gets its access and permissions.                                         |

Workspace admins can manage every team. Only workspace admins can create or delete a team. The Everyone team cannot be deleted.

## Client access

A team's **Client access** tab lists the client segments the team is granted. Members of the team see the clients in those segments. Click **Add client segments** to grant more.

Workspace admins always see every client.

## Permissions

A team's **Permissions** tab lists four actions. Each one is set to **Allowed** or **Not allowed** for the members of that team.

| Permission               | What it covers                                                                                        |
| ------------------------ | ----------------------------------------------------------------------------------------------------- |
| **Send to tax software** | Write a client's Data Entry plan into the tax software.                                               |
| **Delete documents**     | Delete uploaded files and forms from a client's binder.                                               |
| **Download workpapers**  | Download the binder as a PDF, leadsheets, forms or the checklist. Source documents stay downloadable. |
| **Delete clients**       | Permanently remove a client and everything in it.                                                     |

A member can take an action when any of their teams allows it. Workspace admins can always take every action. Only workspace admins can change permissions.

By default, the Everyone team allows every action except **Delete clients**, so all members can do them.

**Walkthrough: limit an action to one team**

1. Open **Settings → Access → Teams** and click **Everyone**, then the **Permissions** tab.
2. Set the action, for example **Send to tax software**, to **Not allowed**. A dialog asks you to confirm, because only admins and members of teams that allow it will be able to do it afterwards. Click **Stop allowing**.
3. Go back to **Teams**, open the team that should keep the action, for example **Tax**, and set the action to **Allowed** on its **Permissions** tab.

Members who are not in that team now see the control disabled. Hovering over it shows the reason, for example "Only the Tax team can delete clients." Members of the team see it enabled as before.

{% embed url="<https://studio.saltfish.ai/demo-share/5276e192-7c19-4e3f-8f4e-44bda43d89ce>" %}

To give an action back to everyone, set it to **Allowed** on the Everyone team.


---

# 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.filed.com/reference/workspace-and-settings/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.
