> 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

<figure><img src="/files/SphQsnfmpiupgpSOt9Ao" alt="" width="273"><figcaption></figcaption></figure>

You can find your team settings under **Settings** > **Team**.

Give your team access to either **individual Google Ads accounts or MCCs** linked to Adalysis. If given access to an MCC, the team member will be able to see and manage all accounts within that MCC and its sub MCCs.

Team members will have access to all features except for billing or managing other team members.&#x20;

<figure><img src="/files/U4ndK5okutbUdFm6Lsd0" alt="" width="446"><figcaption></figcaption></figure>

There are **two settings** to define when adding a new team member:

<figure><img src="/files/mKc6MHOVndLycQpRKInd" alt="" width="399"><figcaption></figcaption></figure>

#### Access level:

* **View only** — can see all data but can’t make changes. Use this option if you want to give someone read-only access.
* **View & edit** — can make changes in Adalysis.

#### Changes appear in Change History under:

* **Admin user**: Changes made by this team member will appear in Google's Change History under the Adalysis admin user (account owner). This setting is useful when you want to keep the team permissions in Adalysis **independent** of those in Google Ads. In other words, team members **don't need** direct access to Google Ads accounts for them to be able to make changes to it in Adalysis.
* **Team member**: Changes made by this team member will appear in Google's Change History under their own email address. The team member email address must also have access permission in Google Ads to the relevant account or MCC.&#x20;

{% hint style="warning" %}
*Please note: If a team member has access to an MCC in Google Ads, they must also be added at the MCC level in Adalysis. The access permissions in Adalysis and Google Ads must match exactly for this setting to work correctly.*
{% endhint %}

{% hint style="success" %}
With the above settings, and combined with [account tags](/onboarding/getting-started/core-account-settings/account-tags.md) and [filters](/onboarding/getting-started/account-organization/filters.md), team leads can set up a flexible environment for their teams that supports collaboration while keeping responsibilities clear.
{% endhint %}

#### Customize Adalysis for your team

{% embed url="<https://youtu.be/19cvzIs0nMY>" %}

#### Account tags and filters

Adalysis tags work exactly like Google account labels and can be used to easily pull up specific sets of accounts.

[Find out more](/onboarding/getting-started/core-account-settings/account-tags.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adalysis.com/onboarding/getting-started/core-account-settings/team-members.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.