> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/tutorials-and-guides/guides/how-to-use-team-management-in-mysportmonks.md).

# How to use Team Management in MySportmonks

Use [Team Management in MySportmonks](https://my.sportmonks.com/subscriptions/team-management) to give colleagues access to your subscription with their own account roles. If you arrived from the old “team mode” guide, this is where to find the current controls.

### Open Team Management

1. Sign in to [MySportmonks](https://my.sportmonks.com/).
2. Open **Subscriptions → Team Management** in the navigation.
3. Review the team members and role information shown on the page.

### Invite a member

1. Select **Invite member**.
2. Enter the colleague’s email address.
3. Select a role: **Admin**, **Developer** or **Card Holder**.
4. Check the email address and role, then select **Invite**.

### Choose a role

* **Admin:** Full account control, including subscriptions and billing, member management, API keys, account settings and ownership transfer.
* **Developer:** Can create and revoke API keys, view usage and limits, and use API features. Cannot change billing or subscriptions, or manage members.
* **Card Holder:** Can view invoices and billing history, update payment methods and download receipts. Cannot access API keys or manage members.

The page also shows active members and pending invitations. Use the **Available Roles** information in MySportmonks when choosing access for a colleague.

### If you cannot find the option

Ask your account owner or administrator for help. For questions about access, contact [Sportmonks support](https://www.sportmonks.com/contact-support/).


---

# 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.sportmonks.com/v3/tutorials-and-guides/guides/how-to-use-team-management-in-mysportmonks.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.
