> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/team/what-is-a-team.md).
# What is a team?
A team is the group of all the users of your company. This is where you can see who from your organization has created a Whaly account.
Inside your team, you can share multiple [Organization](/organisation/what-is-an-organisation.md) to collaborate on Business Intelligence projects.
Member of a team can have 2 main roles:
* **Owner**: It means that you have access on the team management page, where you can review all Team Members, [Organizations](/organisation/what-is-an-organisation.md) and configure the team security settings such as enabling Single Sign On
* **Regular member**: You are part of the team and can be invited into each Organization of the team is needed but you don't have any power on the team structure
### Managing the Team
For all **Team Owners**, a **Manage** button is available on the [Organization](/organisation/what-is-an-organisation.md) selector screen ⤵️
Position of the Manage button to access Team Management page
When clicked, the link is redirecting you to the Team Management page ⤵️
From this page, you can manage:
1. Your Single Sign On configuration
2. The [Organizations](/organisation/what-is-an-organisation.md) that are being used by members of your Team
3. The list of all members of your team and their roles (Owner vs Regular Member)
---
# 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.whaly.io/team/what-is-a-team.md?ask=&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.
