> 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/your-account-structure.md).
# Your account structure
One sign-in for all your ad accounts: your Adalysis account
Adalysis now has **a new way to sign in** and manage your accounts. Your Google Ads, Microsoft Ads and Meta logins, your team, your billing, your notifications and your integrations now sit together in one **Adalysis account**. You sign in to it once, with Google.
This page explains what has changed, what each of the new screens does, and anything you need to do.
***
### How it worked before
* Every ad platform login was a separate Adalysis account
* Separate ad accounts were tied together manually.
* Team members were added per ad account.
* Settings (Slack, MCP, GA4, etc.) were per ad account
### How it works now
* **One Adalysis account for all linked ad accounts.** The owner holds the trial, the subscription, the team, the notifications and the integrations.
* **Ad platform logins live inside it.** You connect as many Google Ads, Microsoft Ads and Meta logins as you need. Each login brings in the ad accounts it can reach, exactly as before.
* **You sign in with Google, using your email address only.** Signing in no longer asks for a passkey. Google may only ask for a passkey when you connect or reconnect a Google Ads login.
* **One sign-in for everyone.** Owners, admins and team members all sign in with their own Google account and see every login they've been given access to.
* **Moving between platforms is one click.** The rail on the left takes you between Google Ads, Microsoft Ads and Meta, and back to your Adalysis account.
### Why it's better
* **You no longer have to link a Google Ads account to use Adalysis**. Linking only Microsoft Ads or Meta is now possible.
* **Invite people once.** Invite a team member once, then give them access to any of your logins, all of the ad accounts in a login, one manager account (MCC) and everything under it, or chosen ad accounts only.
* **The account owner can now create admin users** who can manage the team on behalf of the owner.
* **All ad accounts in one place**, with the same sign-in and the same team.
* **Integrations for every login at once:** several Slack channels, several Google Analytics connections, and an MCP connection that reaches all your ad accounts.
* **You hear about broken connections.** If a login loses access, you get an alert by email and Slack, and you can reconnect it in a click.
***
### The screens in your Adalysis account
Open your Adalysis account with the **Adalysis account** tile at the top of the rail. Which menu items you see depends on your role: **Owner**, **Admin** or **Team member**.
| Screen | Who sees it |
| ------------- | ---------------------------------------------------------------- |
| Overview | Everyone |
| Team | Owner and Admins |
| Billing | Owner only |
| Notifications | Owner and Admins |
| Integrations | Everyone (the Google Analytics tab is for Owner and Admins only) |
| Profile | Everyone |
#### Overview screen
Overview lists your **ad platform logins**. Owners and Admins also see how many ad accounts each login has and how much it spent last month.
From here you can:
* **Connect a login:** *Connect a Google Ads account*, *Connect a Microsoft Ads account* or *Connect a Meta account*. You sign in to the ad platform yourself to connect it, so Google may ask for a passkey at this point.
* **Reconnect** a login that has lost access to its ad accounts.
* **Replace email:** move a Google Ads or Microsoft Ads login over to a different email address. The login keeps its ad accounts, data, settings and team access. If the new email can't reach some of the ad accounts, you see which ones before you confirm.
* **Disconnect** a login. This deletes the login and all its data from Adalysis and can't be undone. Nothing changes in the ad accounts themselves.
To open a login, use the rail on the left. Then switch between the logins of that platform with the email switcher at the top of the app.
#### Team screen
Team lists everyone in your Adalysis account: their role, what they can access, and when they last signed in.
The person invited gets an email, clicks **Accept with Google**, and signs in with the Google account of the email address you invited. Their access is then already in place.
Admins can invite Team members only. They can give access only to logins and ad accounts they can open themselves, at their own access level or below.
#### Billing screen
* View your subscription status, last month's spend for each login, the total, and the plan that matches it.
* **Subscribe:** choose USD or EUR and complete the checkout.
* Once you've subscribed: **Invoices and payment method** opens the billing portal, where you'll find your invoices. You can also change the billing email that invoices and receipts go to.
#### Notifications screen
* **Contact email:** alerts and notices for every login go here, unless a login has its own address. You set a login's own address in that login's *Settings > Notifications* in the app. Only the Owner can change the contact email.
* **Slack:** connect one or more Slack channels with **Connect a Slack channel**. Then, under **Ad platform logins**, choose which channel each login posts to, or *No Slack*. You used to have one Slack channel per Adalysis account. Now you can connect as many channels as you need, across one or more workspaces, and send each login's alerts to its own channel. For example, each client can have their own channel.
Which alerts each person gets, by email or Slack, and at what time, is still set in each login's *Settings > Notifications* in the app.
#### Integrations screen
**Google Analytics**
Connect one or more Google accounts that can read your Google Analytics 4 properties. Every Google Ads login in your Adalysis account can then use them. To link an ad account to a property, open the login in the app and go to *Settings > Integrations > Google Analytics*. From this screen you can also **Reconnect** or **Remove** a connection.
**MCP server**
Connect AI assistants like Claude and ChatGPT to your Adalysis data. Copy the Adalysis MCP server address, add it as a connector in your assistant, and sign in with your Adalysis account when asked. A key is created for you automatically.
**One connection now reaches every Google Ads login you can open, with your own access.** Microsoft Ads and Meta are coming later.
**Connected assistants and API keys** lists each assistant you've connected. Click **Revoke** to disconnect one immediately.
***
### What you need to do after the move
Review the below using the new screens (described above):
1. **Review your team members** permissions. To change someone's role or scope, remove them and invite them again with the new role.
2. **Review your Slack setup.** Your existing Slack channels have been carried over. Go to **Notifications** to check which channel each login posts to, and connect any extra channels you want.
3. **Upgrade your MCP keys.** On **Integrations > MCP server**, click **Upgrade all** under *Keys of a single login*. Upgraded keys keep working without any change in your assistant, and reach all your Google Ads logins.
### Questions?
Contact our support team. We're happy to help you move or check your setup.
---
# 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/your-account-structure.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.
