> For the complete documentation index, see [llms.txt](https://www.bluegamma.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bluegamma.io/documentation/account-and-team-management.md).

# Account & Team Management

- [Trials and Billing](https://www.bluegamma.io/documentation/account-and-team-management/trials-and-billing.md): How the BlueGamma free trial works, what happens when it ends, how to subscribe, API keys, and billing.
- [Adding and Removing Seats](https://www.bluegamma.io/documentation/account-and-team-management/adding-and-removing-seats.md): How organisation admins invite people, change their access, remove and add back members, and request more seats in Organisation settings.
- [Security and Access](https://www.bluegamma.io/documentation/account-and-team-management/security-and-access.md): Login methods, access control and SSO options for BlueGamma, including technical details on Microsoft login for IT and security teams.
- [Access Control and SSO](https://www.bluegamma.io/documentation/account-and-team-management/security-and-access/access-control-and-sso.md): The login methods BlueGamma supports, the access controls we can configure for your organisation, and Enterprise SSO.
- [Login via Microsoft](https://www.bluegamma.io/documentation/account-and-team-management/security-and-access/login-via-microsoft.md): This page provides technical information for IT and Security teams about how Microsoft login works on BlueGamma, what identity data is used, and how your organisation can control access.


---

# 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://www.bluegamma.io/documentation/account-and-team-management.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.