> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/onboarding/getting-started/core-account-settings/team-members.md).
# Team members
Set up access for your team
Your team is managed in your **Adalysis account**: click the tile at the top of the rail on the left, then **Team**. The Owner and Admins can manage the team.
You invite each person once, then give them access to any of your Google Ads, Microsoft Ads and Meta logins. Everyone signs in with Google using their own email address.
#### Roles
* **Owner:** manages everything, including billing. There is one owner per Adalysis account.
* **Admin:** manages the team, notifications and integrations, and can connect and reconnect logins. Admins can't see billing. They can invite team members only, and can give access only to logins and ad accounts they can open themselves, at their own access level or below.
* **Team member:** works in the ad accounts they've been given access to.
To give someone a different role, remove them and invite them again with the new role.
#### Inviting someone
1. On **Team**, open **Invite a team member**.
2. Enter the email address of their **Google account**.
3. Choose their role (Owner only): **Team member** or **Admin (manages the team)**.
4. For each login, choose:
* **Access:** **No access**, **View only** (can see all data but can't make changes) or **View and edit** (can make changes in Adalysis).
* **Ad accounts:** **All ad accounts**, **One manager account and all under it** (the MCC and all its sub-accounts) or **Chosen ad accounts**.
5. Click **Send invitation**.
The person receives an email, clicks **Accept with Google** and signs in with the Google account of the email address you invited. Their access is then in place. Invitations are valid for 14 days; you can see and cancel pending ones under **Invitations**.
{% hint style="warning" %}
A Google account can belong to only one Adalysis account. If the person already has their own Adalysis account, or is on another team, the invitation is refused.
{% endhint %}
To change what someone can access, click **Change access**. To take away all their access, click **Remove**.
#### Changes in Google's change history
Team members make changes through the owner's own access to Google Ads and Microsoft Ads. Changes they make in Adalysis therefore appear in Google's change history under the **owner's email address**, and team members don't need their own access to the ad accounts.
To see which team member made a change, use **Settings** > **Change history** > **Local change history** in the app.
{% hint style="success" %}
Combined with account tags and filters, team leads can set up a flexible environment for their teams that supports collaboration while keeping responsibilities clear.
{% endhint %}
---
# 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.adalysis.com/onboarding/getting-started/core-account-settings/team-members.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.
