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

# Manage your team

Work together with your team and organization.

## Manage your team

In Quadratic, you are placed in a **Team** by default, even if it's just you.

You can add and switch which **Team** you're working with from the **Teams** selection menu in the top left of your dashboard.

<figure><img src="https://2438361843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff1Y5UzPF2x1oIzVJbUK8%2Fuploads%2FE8MerHp59HXIyHAXFLKt%2FCleanShot%202024-07-17%20at%2016.20.56%402x.png?alt=media&#x26;token=2bf363e0-6fa9-4b36-bd01-e6707bf513ed" alt="" width="563"><figcaption></figcaption></figure>

### Add team members

You can view your team members from the Members tab on your team's dashboard. You can also add, remove, and edit their permissions from here.

<figure><img src="https://2438361843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff1Y5UzPF2x1oIzVJbUK8%2Fuploads%2FW5xUSujCjtRXVINrHQPG%2FCleanShot%202024-07-17%20at%2016.43.36%402x.png?alt=media&#x26;token=895b2596-753b-4de3-8847-ecbb5adb6b3e" alt=""><figcaption></figcaption></figure>

### Team permissions

By default, members of your team(s) will have access to all of your sheets within the team.

You set each member's team permissions. These permissions are global to your team and apply to all spreadsheets within that team.

* **Owner:** creator of the team, can add and remove members, edit all files, create and remove connections.
* **Editor:** can edit all files and access all connections but cannot add or remove members and cannot edit or remove connections.
* **Viewer:** can view all files but not edit files, cannot add and remove members, and cannot add, edit, or remove connections.

To edit permissions, open the Members tab and make your changes to each user's permissions.

### Manage your connections

Manage your connections from the Connections tab. Connections are a direct connection to databases, data warehouses, and SaaS tools.

Learn more about SQL connections and Agent connections.

<figure><img src="https://2438361843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff1Y5UzPF2x1oIzVJbUK8%2Fuploads%2Fm6IMbIdupYYryhuYIU5W%2FCleanShot%202024-07-17%20at%2016.55.07%402x.png?alt=media&#x26;token=44c514ff-8ac1-4887-9a13-a10b7a52f6e6" alt="" width="563"><figcaption></figcaption></figure>

### Team secrets

Store API keys and credentials as named secrets from your team settings. Secrets are referenced as `{{SECRET_NAME}}` from agent connections and code cells, and their values are never exposed after creation.

### API tokens

Create tokens for the Developer API from your team settings. Tokens are team-scoped — treat them like passwords.

### Team AI memory

Shared AI context for your whole team lives in your team settings. Add business definitions and conventions once, and every teammate's AI chats use them. See AI memory & context.

### Plans & billing

Your team's plan, AI usage, and invoices are managed from the Billing settings. See Plans & billing.

### Rename your team

Navigate to the **Settings** tab and change your team name.

<figure><img src="https://2438361843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff1Y5UzPF2x1oIzVJbUK8%2Fuploads%2FFeIEe9dHM1SZhKhedVLT%2FCleanShot%202024-07-17%20at%2016.46.42%402x.png?alt=media&#x26;token=fb55d659-8d94-43cf-9358-c34ac9c6c9d4" alt=""><figcaption></figcaption></figure>


---

# 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.quadratichq.com/teams/manage-your-team.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.
