> ## Documentation Index
> Fetch the complete documentation index at: https://docs-hub.magicmealkits.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Accounts and clients

> What an account, an OAuth client and a connector each are, and why one client covers every account. Read this if the words are running together.

Three things in the hub have names that sound alike, and one word does double
duty in the industry. This page separates them once, so the rest of the
documentation reads cleanly.

## An account is a Google account

An account is one Google account you have attached to the hub: your personal
Gmail, your work Workspace address, the one that came with a domain you bought.
You give each one a short name, and that name is what you say to Claude when
you want it to work in that account.

Accounts sit under **Accounts** in the admin screen. Nothing is connected until
you add it there, and removing it there disconnects it.

## A client is the key Google gives you

An OAuth client is what the hub signs an account in with. Think of it as a key.
You make one in the Google Cloud console, once, and Google hands you two values:
a client id and a client secret. Those two values are the key.

**A client is not Claude.** This is the part that catches people out, because
"client" also means a program that connects to something. Here it means the
credential your hub logs in with, nothing else. It is called a client because
that is what the Google console calls it, and you will need to find it there.

Clients sit under **Clients** in the admin screen, and
[making one](/oauth-client) is a ten minute job you do once.

## A connector is Claude, or ChatGPT

A connector is the program on the other side: Claude, ChatGPT, anything that
speaks MCP. Claude calls them connectors too, on its own settings screen. You
add the hub's address there once, and that connector can then reach every
account you have attached.

Connectors you have approved are listed under **Approved connectors** in the
admin screen, and you can revoke one there.

## How they fit together

```mermaid theme={null}
flowchart LR
  C["Claude<br/>(connector)"] --> H["Your hub"]
  H --> K["One client<br/>(the key)"]
  K --> A1["Account: personal"]
  K --> A2["Account: work"]
```

## Several accounts, one client

The key does not belong to an account. It belongs to your Google Cloud project,
and it opens every account you sign in with it. So you make one client and reuse
it: the first account you add is the only time you paste a client id and secret
in. After that the hub already has it, and adding an account is a name, a pick
from a list, and the services you want.

Most people never need a second one. The exception is a Workspace organisation
that blocks unverified apps, or one where you would rather its members did not
see the unverified warning. That means a second client in a project that
organisation owns, and
[how many projects you need](/oauth-client#how-many-projects-you-need)
covers it.

A second client is not how you move accounts around. If an account ended up on
the wrong one, [fixing it](/fixing-the-wrong-client) is a different job.

## Next

* [Setting up](/quickstart), from the beginning
* [Making an OAuth client](/oauth-client)
