> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/teams-and-billing.md).

# Teams & billing

- [Teams & billing](https://help.intangible.ai/teams-and-billing/teams-and-billing.md): Workspaces, plans, invites, project ownership. Everything tied to who's on your team and what tier you're on.
- [Workspaces](https://help.intangible.ai/teams-and-billing/workspaces.md): Personal workspace versus team workspace. What changes when you switch, and why team workspaces are the right home for shared client work.
- [Create and invite](https://help.intangible.ai/teams-and-billing/create-and-invite.md): Make a team, add seats, send invites. The full setup flow for a multi-user workspace from scratch.
- [Plans and billing](https://help.intangible.ai/teams-and-billing/plans-and-billing.md): Free, Explorer, Business plans. Payment methods, multiple owners, credit packs, annual discounts.
- [Permissions](https://help.intangible.ai/teams-and-billing/permissions.md): Member versus Owner permissions on a team workspace. Who can edit projects, who can manage seats, who can change billing.
- [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md): Transfer a project to another team member. The right tool when the original creator is leaving the team or handing off the lead.


---

# 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://help.intangible.ai/teams-and-billing.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.