AdCopilot docsby Atromx
Guides

Team and seats

Invite teammates by their Google address to share connected accounts. Each plan includes seats, and paid plans add more at $19 a month each.

View as Markdown
Open inClaudePerplexity

A workspace can be shared. Invite teammates so more than one person can work with the same connected Google Ads accounts from their own AI clients.

Inviting teammates

Every workspace is invite-only. On the Team page at app.adcopilot.cloud, the workspace owner invites a teammate by the address of their Google account, as a member or a viewer. Each teammate signs in with their own Google account and works within the workspace's connected accounts. Step by step, with screenshots: Invite a teammate.

  • An invitation is a link for one address. It works only for a Google sign-in as the address you invited (an address with a + is the exception, below), for 7 days, and only once, so invite the address they sign in to Google with. The Team page shows the link for you to copy and send, or says when it was emailed.
  • An address with a + in it reaches the same inbox as the address without the part after the +, so the invitation is emailed there and works for a Google sign-in to that inbox: the address without the part after the +, or any + spelling of it. It still takes one seat, for whichever of them signs in first. The part after the + can only be a short tag: letters, numbers, dots, dashes and underscores, with no link or IP address in it, and the address needs something before the +.
  • Waiting invitations are listed on the Team page, with the address, the role and the date they stop working. Revoke ends one at once. Inviting the same address again, in any spelling of the same inbox, replaces its invitation.
  • An invitation holds a seat until it is used, revoked or expires. When every seat is taken or invited, the Team page says so instead of showing the form. If waiting invitations fill it, revoke one you no longer need; if people fill every seat, add a seat or remove someone (below).
  • An invitation waits for a free seat. When people take every seat (for example, a trial ends and the plan has one seat), waiting invitations are on hold: nobody can accept one, and none is emailed again, until a seat is free. They stay listed so you can revoke them. When there are more invitations than free seats (after a move to a plan with fewer seats), the newest are on hold: they aren't emailed and their links aren't shown. A link you already sent still works, first come, first served, until the seats are taken, so revoke any you don't want used.
  • Only the owner sees the invitations. Members and viewers don't.

Workspaces that had a shared join link no longer use it: anyone who opens an old link is told to ask the owner for an invitation. Teammates who joined through it keep their seats.

Seats are not the tier — they are an add-on

Plans are sized by how many Google Ads accounts a workspace runs — see Billing and plans. Teammates are a separate, orthogonal axis: each plan includes a number of seats, and a paid plan can add more, up to the most people it holds. The owner counts as one seat.

PlanSeats includedMost people
Free11
Starter12
Plus34
Scale59
Pro10100

An extra seat is $19 a month, or $190 a year on yearly billing, plus any tax, on every paid plan. Free includes one seat and takes no extra seats: a Free workspace that needs a second person moves to a paid plan first. A team that already has more people than its plan's limit keeps them, but can't add more.

On a paid plan, each person has their own daily operations. On Plus, every member and viewer has 2,000 operations a day of their own. During a trial the count is the workspace's, and so is the grace day (one day in any 7, whoever goes over). The Google Ads accounts switched on are the workspace's.

Adding a seat

Only the owner adds or removes seats.

  • When you subscribe on a plan paid in US dollars or euros, pick extra seats on the Billing page where it offers them, before you pay.
  • On a paid plan, press Add a seat on the Team page where it shows one. It shows what you pay today for the rest of your billing period and what you pay from your next billing date. Confirm, and the seat is yours as soon as the payment goes through. Your billing date doesn't change.
  • Where neither page offers a seat, or the plan is paid in rupees, write to support@adcopilot.cloud and we add it.

You get a receipt by email for each change.

Removing a seat or a person

  • Remove a seat on the Team page frees an empty seat. The unused days are taken off your next bill. A seat someone uses, or a waiting invitation holds, can't be removed: remove the person or revoke the invitation first.
  • Remove on a member's row takes them out of the workspace. Their assistant stops working here. Nobody's Google account is touched. To bring them back later, write to support.
  • A seat change waits while a plan change or a cancellation is scheduled. Press Keep my plan first, or write to us.

When the seats fall below the people

If the seats drop without you removing anyone, for example when a trial ends on Free, the newest members are paused, never the owner. A paused member and the owner get an email. The Team page lists them as paused, and they come back on their own when you add a seat or move to a paid plan that holds them.

Roles and access

  • The owner manages billing, the plan, and who is in the workspace.
  • Members work with the connected accounts through their own AI clients, under the rules that apply to everyone: each change is proposed first, for a hard stop each member sets their AI client to ask before AdCopilot's write tools (Needs approval in Claude; in Cursor, the Allowlist run mode with them off the allowlist; see Approval-gated writes), and nothing can be deleted.
  • Viewers can read but not change anything (see Read vs write tools). The owner sets each teammate's role on the Team page.

Share a teammate's Google login

Each person's calls use their own Google login whenever it reaches the account. When an account is reached only through a teammate's login, the owner can share that login with someone on the Team page, under Google logins, so that person can work on it without anyone sharing a Google password.

A Google Ads change always runs on the Google login of the person making it. In Google Ads, a shared login lets that person read the account, and a change there needs their own login. Can make changes applies to Google Analytics 4, Tag Manager and Search Console.

How sharing works

  1. The person who connected a Google login switches on Let teammates use this login on their own card, Your Google login. Only they can switch it on, and it is off for every login until they do.
  2. The owner picks the teammate, the accounts, and Read-only or Can make changes. Can make changes covers Analytics, Tag Manager and Search Console; in Google Ads the login reads only, whichever is picked. A viewer gets Read-only. Nothing is shared until the owner picks accounts: chosen accounts, every account of a product, or every account of the login, including ones found later.
  3. That teammate's requests on those accounts go through that login wherever their own login doesn't reach them. Every call made through it is recorded, and the person whose login it is sees the latest under Recent use of your login on their card.
  4. The owner, or the person whose login it is, can stop it at any time.

The details

  • Switching on needs the updated privacy policy accepted. Sharing more later (more accounts, or Can make changes) needs the same yes: the switch on, the policy accepted, and their seat on. Sharing less never does. The person whose login it is gets an email the first time it is shared. Switching it off ends every share of the login at once; Stop ends one. Disconnect Google ends them all too, and the login comes back unshared when they connect again.
  • A Google Ads change runs only on your own login. Through a shared login it is refused, whatever the share allows; reads through the shared login still work. To make the change, connect your own Google login that has access to the account, or ask a teammate whose login reaches it to make it.
  • Google's own history shows the login's account for a change made through it in Analytics or Tag Manager, so AdCopilot lists the calls made through someone else's login for the owner (Recent use of shared logins) and for the person whose login it is.
  • Shared with you on your own card says, for each login shared with you, whose it is, which accounts, and whether you may make changes. The owner changes it.
  • When more than one login reaches an account, the owner can choose which one serves it under Accounts more than one login reaches. A person's calls use their own login first, then the chosen one if they may use it, then another login shared with them that reaches the account.
  • A paused seat's login serves no share until the seat is back: the person can't reach their card to stop it, so nobody else uses it meanwhile. When someone leaves the workspace, the shares of their login end 14 days later, and they get a two-line email.
  • These sections appear once the workspace has two or more people, and sharing works once AdCopilot has switched it on for your workspace; until then the page says so and each person uses their own login.

What a refused call says, and what to do, is in Teammate problems.

Multiple workspaces

You can belong to more than one workspace — for example your own and a client's. Switch between them from the sidebar; each has its own connected accounts. The connector URL is the same for all of them: when you approve an assistant, you pick the workspace it may use. See Accounts and scope. A plan applies to one workspace only: see Which workspace a plan applies to.

On this page