# Can one AI notetaker cover meetings from several Google accounts?

> For freelancers and consultants who hold a separate Google account for each client: why forwarding every invitation to one calendar or adding the bot by hand goes wrong, what a per-account connection should do with reschedules, cancellations and expired access, and where its limits are. Covers Google Meet and Microsoft Teams meetings, and ends with how TrackHeros ties each account to one client.

Canonical: https://trackheros.com/blog/one-notetaker-several-google-accounts/  
Author: Sami Kanafani  
Updated: 2026-10-05

**In short:** Yes. TrackHeros connects every Google account you hold, as many as you have, under one sign-up, and ties each account to exactly one client workspace. Google Meet and Microsoft Teams meetings on each account's primary calendar are filed under that client, follow reschedules and cancellations on their own, and are joined by a bot under that client's name. Microsoft accounts connect the same way.

| Fact | Detail |
| --- | --- |
| Google accounts per sign-up | As many as you hold |
| Clients per connected account | Exactly one, enforced in the database |
| Calendar read | Each account's primary calendar, read-only |
| Reschedules and cancellations | Followed automatically; a cancelled meeting cancels the bot |
| How far ahead | About two months |

One AI notetaker can cover meetings from several Google accounts, as long as it connects each account on its own and knows which client each one belongs to. Forwarding every invitation into one calendar, or pasting the bot into each meeting by hand, works for a week and then misses a reschedule. This guide is for freelancers, consultants and fractional CTOs who hold a Google account per client and take their calls on Google Meet and Microsoft Teams. The product side is on [one notetaker for every account you hold](/features/multi-account/).

## Why do freelancers end up with one Google account per client?

Because each client's tools assume you are staff. A client on Google Workspace gives you `you@client.com` so you can open their documents, join their groups and receive their invitations without an access request every time. Six clients, six accounts, six calendars.

The accounts are not interchangeable. An invitation sent to `you@client-a.com` lives in that account's calendar, carries that client's Meet link and expects a reply from that address. Your personal Gmail sees none of it. A notetaker that reads one calendar per login sees one client's week and nothing of the other five. The browser side of this is in [managing several Google accounts as a freelancer](/blog/multiple-google-accounts-freelancer/); this guide is about the notetaker.

## Why not forward every invitation to one calendar?

Because a forwarded or copied invitation is a snapshot, and meetings move. The usual workarounds each fail in their own way:

| Workaround                                      | What goes wrong                                                                                                                                |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Copy each client event into your main calendar  | The copy does not move when the organiser does. The bot turns up at the old time, to an empty room                                             |
| Forward invitation emails to one address        | The same snapshot, and the organiser may find an address on the guest list they never invited                                                  |
| Subscribe your main account to client calendars | A notetaker usually reads the calendar of the account you connected, not the ones it subscribes to. Free/busy sharing shows "Busy" and no link |
| Add your main address as a guest on every call  | You ask every organiser, every time, and the client's records now hold your personal address                                                   |

The deeper problem is filing. When every client's meetings arrive in one calendar, nothing tells the notetaker that Tuesday's 10:00 belongs to Client A and the 11:00 to Client B. It either puts them all in one place or asks you, meeting by meeting. One pile is how notes end up mixed, which is the subject of [keeping client meeting notes separate](/blog/keep-client-meeting-notes-separate/).

## What goes wrong when you add the bot to each meeting by hand?

You forget, the meeting moves, or you file it under the wrong client. Pasting a link is a fine fallback for a one-off call and a poor system for four clients' weekly calls.

Forgetting is the obvious one. A recurring call needs the bot every week, and the week you are late is the week you skip it.

Reschedules are worse, because they look handled. You booked the bot for Thursday at 14:00; the client moved the call to 15:30 in their calendar, which you never opened. The bot is booked for a time that no longer exists.

The wrong client is the expensive one. You paste Client B's link while Client A's workspace is open, and the recording, transcript and notes are filed under A. If the notetaker lets you name the bot per client, it also arrives under A's name, which is the first thing Client B's team sees in the participant list.

## What should a per-account connection do?

It should treat each Google account as its own source, tied to one client before anything arrives. Then a meeting's client is settled by where the invitation landed, not by a guess or by your memory. Whatever notetaker you use, check for:

- Several accounts of the same provider under one sign-up, not one account per login.
- Each account tied to exactly one client, so a meeting on its calendar can only be filed one way.
- Read-only calendar access. A notetaker needs to see the event, not your inbox.
- Changes pushed by Google as they happen, not a nightly import.
- One view of the week across every account, with each meeting labelled by client.
- A visible signal when an account stops syncing.

## What should happen when a client moves or cancels a meeting?

The bot should move or stand down on its own, because the notetaker heard about the change from the calendar, not from you. The organiser's invitation is the source of truth; anything that copies it once is out of date the first time it changes.

Google can notify an app when a calendar changes, through a watch channel. Those channels expire, and an app that does not renew them goes quiet without an error. A periodic full re-read behind the notifications catches anything a notification missed. Ask any vendor two questions: what happens to the bot when a meeting moves, and what happens when it is cancelled. "It moves" and "it stands down" are the only good answers.

## What happens when a client's Google account stops working?

The notetaker loses access to that calendar, and the risk is that nobody notices. A password change, a new security policy from the client's admin or a suspended account at the end of a contract can each cut a notetaker off, and the first sign is often a missed meeting.

Two habits help. Look at your notetaker's list of connected accounts after a client changes their security settings. And reconnect from that client's browser profile: Google's account chooser offers every account signed into the browser, and with six of them it is easy to pick the wrong one. A careful notetaker refuses a reconnection that comes back as a different account rather than attaching it to the wrong client.

## How does TrackHeros handle it?

TrackHeros is an AI meeting notetaker that connects every Google and Microsoft calendar you hold, detects the language of each meeting on its own, and keeps every client's notes in a sealed workspace of its own. For several Google accounts, that works like this:

| Step     | What happens                                                                                                                                        |
| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Connect  | On a client's page, Connect Google, sign in with that client's account and grant read-only calendar access. Repeat for each client; there is no cap |
| Binding  | Each account belongs to exactly one client, enforced in the database. The same account cannot be attached to a second client                        |
| Filing   | Every event on that account's primary calendar carrying a Google Meet or Teams link is filed under that client before the bot joins                 |
| Sync     | Google watch channels, renewed before they expire, plus a full re-read every 15 minutes. A reschedule moves the bot; a cancellation cancels it      |
| Joining  | About two minutes before the start, under the bot name set for that client. It does not need to be the host and waits in the lobby to be admitted   |
| One view | The [unified calendar](/features/unified-calendar/) shows every account's meetings, coloured and labelled by client, read-only                      |

When an account needs reconnecting, the client page shows "Reconnect needed" and that account's sync stops until you reconnect. There is no email about it. The reconnection is bound to the account you clicked: if Google hands back a different address, TrackHeros says "You signed in as X, but this reconnection is for Y. Nothing was changed".

Microsoft accounts work the same way: Microsoft 365 work or school accounts and personal Outlook.com ones, under the same sign-up and the same one-client rule. A meeting that sits on a Google and a Microsoft calendar of the same client is recognised as one meeting and gets one bot. The details are in [connecting Google and Outlook calendars to one notetaker](/blog/connect-google-and-outlook-calendar-to-one-notetaker/).

## What does TrackHeros not do?

- It reads only each account's primary calendar. Other calendars on the account, ones you created, subscribed to or were given access to, are not read.
- It lists only events with a recognised Google Meet or Microsoft Teams link, found in the conference data, the location or the description. Other events do not appear.
- It reads from yesterday to about two months ahead.
- It does not match the same call across two clients. Each client gets its own record and bot; switch auto-join off for it in one.
- It does not let one account serve two clients. If one calendar holds several clients' meetings, connect it as your personal calendar instead: its meetings arrive unfiled and private to you, and the bot joins only once you file one under a client. See [a personal calendar beside client calendars](/blog/personal-calendar-and-client-calendars/).
- It has no "move this calendar to another client". Disconnect it and connect it under the other client; meetings already filed stay where they are. Disconnecting does not cancel bots already scheduled from that account, so switch auto-join off for any you no longer want.

## Frequently asked

**How many Google accounts can I connect to one TrackHeros sign-up?**

As many as you hold; there is no cap. Each account is tied to one client workspace when you connect it, and its primary calendar is synced on its own. A consultant with six clients and six Google accounts connects all six under the same sign-up.

**Can I use one Google account for two clients?**

Not as a client account. Each connected account belongs to exactly one client, and connecting it to a second one is refused with "already connected to another client. Disconnect it there first." If one calendar holds several clients' meetings, connect it as your personal calendar in Settings and file each meeting, or each recurring series, under its client.

**What happens to scheduled bots if I disconnect a Google account?**

Sync stops for that account only, and TrackHeros revokes its Google access. Upcoming meetings already synced from it are not cancelled: their bots stay scheduled and no longer follow reschedules, so switch auto-join off for any you no longer want. Past meetings stay filed under the client.

**Does connecting a Google account let the notetaker read my email?**

No. Calendar sync asks Google for your sign-in address and read-only access to the calendar, and nothing else. Nothing in calendar sync reads mail, files or contacts.

**Will the same meeting on two of my Google accounts get two bots?**

Not if both accounts belong to the same client. TrackHeros recognises the meeting by its calendar id and start time, or by the same link at the same time, and sends one bot. If the accounts belong to different clients, each client gets its own record and its own bot by design, so switch auto-join off for that meeting in one of them.

---

TrackHeros is in early access: https://trackheros.com/#early-access