Why most meeting notetakers allow one calendar per login

Most AI notetakers let you connect one calendar per login, because they are built for people who work for one company. This guide explains that design choice fairly, what it costs someone who holds a separate Google or Microsoft account for each client, and what a notetaker needs underneath to handle several clients properly. It is for freelance developers, consultants and fractional CTOs whose client calls run on Google Meet and Microsoft Teams. The short version of how TrackHeros does it is on the multi-account page.

Why do most notetakers allow only one calendar per login?

Because they are designed for internal teams, where one person works for one company and has one work account. The sign-in is the identity, the identity comes with a calendar, and that calendar is the person's working week. A second calendar is an edge case the model never needed.

This is a sensible design, not an oversight. The buyer is usually a company. It wants every employee's meetings recorded under its own domain, visible to the right colleagues, governed by one administrator and billed per seat. Tie the notetaker to the work login and all of that follows: one workspace per company, sharing between colleagues as the default, one bill. For a sales team or an engineering department, that is exactly right.

What does "one login, one workspace" assume about you?

It assumes that the account you sign in with is the company you work for. Your identity, your calendar, your workspace and your bill all hang off that one sign-in.

• Your identity is your work address. The notetaker knows you as you@company.com and nothing else.
• Your calendar is that account's calendar. Invitations sent to any other address are invisible to it.
• Your workspace is the company. Everything recorded lands in one pool, searchable together and shared with colleagues by default.
• Your bill is a seat. A second login is a second seat, or a second subscription.

For an employee, each assumption is true. For a freelancer with six clients and six accounts, each one is false in a different way.

What breaks when you hold six client accounts?

Three things: you keep switching logins, meetings get missed, and notes from different clients end up in one searchable pile. None of them is dramatic on the first day. All of them compound.

Switching logins

Connect one client's account and the other five are invisible. Either you run six subscriptions with six sign-ins, or you pick the busiest client and take notes for the rest by hand. Settings follow the login too, so changing what the bot calls itself or switching off auto-join for one call means first remembering which login you are in.

Missed meetings

The invitation arrives on Client C's address. The notetaker watches Client A's calendar. Nobody joins, and you find out afterwards, when you go looking for notes that do not exist. A reschedule on a calendar the tool cannot see is the same failure a week later.

Notes from Client A next to Client B

The usual workaround is to forward every invitation into one calendar the notetaker can see. Now it catches every meeting and files them all in one workspace. Search for "pricing" and Client A's rate card comes back next to Client B's budget. Ask the built-in assistant a question and it answers from both. The bot introduces itself under one name on every call, and removing one client's history at the end of a contract means picking it out by hand.

Why not forward every client invitation to one calendar?

Because it fixes the missed meetings by creating the mixing problem, and it may break your clients' rules. A forwarded invitation copies the client's meeting details, attendee addresses and joining link into an account the client does not control.

Many companies issue you an account precisely so their meetings stay inside their organisation. Copying them out to your own calendar is the thing that account was meant to prevent. Forwarded invitations also travel badly: a Microsoft Teams invite forwarded into Google Calendar often arrives with no Join button, and the only link is buried in the description. A notetaker that reads only the conference data will miss it. The guide to running several Google accounts covers where links hide and how to keep every calendar in view without merging them.

What does a notetaker need underneath to handle several clients?

Five things: each account bound to one client, every query scoped to one client, settings per client, deletion per client, and no matching across clients. Without them, connecting more calendars only makes a larger pile.

Requirement	What it means	Why it matters
Account bound to client	Each connected account belongs to exactly one client, decided when you connect it	A meeting has an owner before the bot joins, so nothing is filed by guesswork
Every query scoped	Every read of meeting data names one client before it runs	Search, summaries and the assistant cannot pull from the wrong client
Settings per client	The bot's name and its greeting are set per client	Client B's call does not hear Client A's name
Deletion per client	One client's meetings, recordings and transcripts can be removed on their own	Ending one engagement does not touch the others
No cross-client matching	The same call on two clients' calendars stays two records	Matching them would mean reading one client's records from inside another's

The last one surprises people. A tool that removes duplicates across everything you have connected has to compare Client A's meetings with Client B's to do it, and that comparison is itself a read across the boundary. The honest trade is an occasional duplicate that you switch off yourself, which is covered in the guide to the same meeting on two calendars.

You also need one place to see the week. Not a merged pool, but a view that puts every client's meetings on one timeline and labels each one with its client, so you can see the clash at 3pm without the notes underneath ever mixing.

How can you tell whether a notetaker is built this way?

Ask five questions before you connect anything. The answers show whether clients are a real boundary or a folder.

1. Can I connect a second Google or Microsoft account without a second sign-up?
2. Does each connected account belong to one client, or to one shared pool?
3. When I search for a word, do results from different clients come back mixed, or labelled with their client?
4. Can the bot use a different name on each client's calls?
5. Can I delete one client's data and leave the rest exactly as it was?

A tool built for one company will answer most of these with "use a separate account". That is a fair answer for its customers. It is not a design for yours.

How does TrackHeros handle several client calendars?

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. It was built the other way round from the category: the client is the unit, not the company you log in as.

• Every account, one sign-up. You connect as many Google and Microsoft accounts as you hold, including Microsoft 365 work or school accounts and personal Outlook.com ones. There is no cap.
• Each account belongs to exactly one client, enforced by a database constraint. Attach an account another client already uses and TrackHeros refuses: "already connected to another client. Disconnect it there first."
• Only the main calendar is read: the primary calendar in Google, the default calendar in Microsoft. The calendar permission is read-only.
• Every query is scoped to one client before it runs, and Postgres row-level security checks the same rule again underneath. See client workspaces that never mix.
• Settings per client. The bot joins as "TrackHeros Notetaker" by default, and you can rename it for each client.
• Deletion per client. Deleting a client workspace removes that client's data and leaves the others untouched. What we promise about your data is in the privacy section.
• Matching inside a client, never across. The same meeting on two calendars of one client, including one Google and one Microsoft, is one meeting with one bot. The same call on two different clients' calendars is a record and a bot in each; switch auto-join off for it in one of them.
• One view of the week. The read-only unified calendar shows the meetings from every connected calendar, coloured and labelled by client.