Team 3
£10.00 a month Per account, paid annually at £119.99 + VAT
- 3 named people, across every mailbox on the account
- Own connector URL and permission level per person
- Own daily cap per person, set by you
- Remove a person in one action
Team Access pricing
Team Access: people bought once, for the account.
Team Access gives a colleague, an assistant or a contractor their own connection to a mailbox you own, with a permission level and a daily cap you set, and their own line in the activity record. It is bought once, for the account, as a tier of 3, 5 or 10 named people, on top of Pro on the mailboxes themselves.
- Tiers 3, 5 or 10 people
- From £119.99 + VAT a year
- Mailboxes Pro, per mailbox, £34.99 + VAT
The tiers
The 3 Team Access tiers
A tier is a number of named people. Each may be given their own connection to any Pro mailbox on your account, and one person on several mailboxes is still one person.
Team 5
£16.67 a month Per account, paid annually at £199.99 + VAT
- 5 named people, across every mailbox on the account
- Own connector URL and permission level per person
- Own daily cap per person, set by you
- Remove a person in one action
Team 10
£33.34 a month Per account, paid annually at £399.99 + VAT
- 10 named people, across every mailbox on the account
- Own connector URL and permission level per person
- Own daily cap per person, set by you
- Remove a person in one action
Mailboxes are bought per mailbox. People are bought once, for the account.
-
A tier includes no mailbox.
Each mailbox you share has to be on Pro, at £34.99 + VAT a year, bought per mailbox. The tier sits on top.
-
The 3 prices above are the whole price list.
There's no per-head discount, and no "whole team included" figure.
-
One annual payment, by card.
Paid through Stripe, net of VAT, and renewing annually until you stop it.
-
This page is the price.
Everything a team gets is on the teams page.
Per person
What each person gets
You invite a person by email address and choose which of your mailboxes they may reach. Then you set 3 things for them: a permission level, whether the calendar is included, and a daily cap.
Each person gets their own connector URL, one per mailbox they're on, which they paste into their own AI client. Nothing of yours is shared with them: not your password, not your token, not your connection.
The level is the same 3-step ladder every connection on this site carries: Read only, Draft and file, or Send and delete, with the calendar on or off beside it. The tool reference lists every tool under the level that reaches it.
Changes land without anybody reconnecting. Level, calendar, cap and display name are changed from the People tab. They land on every mailbox the person is on at once, on their next call.
An invitation is bound to the address it was sent to. Only an account whose verified email address is the invited one can accept it, so a forwarded link doesn't work for anybody else. The refusal names the account that's signed in, and shows the invited address in masked form.
Every call carries the person's name. Once they've accepted, every call they make is in the activity record under their name. So the log on a shared mailbox says who did what, not only what was done.
Removing a person is one action. Every share they held and every connection they made end together, each connection on its next call, and they're emailed to say so. Pausing a person is the same control without the email, and resuming them takes one seat check.
A person who isn't entitled is refused, not deleted. That's when the tier lapsed, you downgraded, or you paused them. They get a plain sentence in the control panel and an opaque refusal in their AI client. Nothing of theirs is deleted, and a tier that covers them again seats them without re-inviting.
Metering
How a shared mailbox's daily allowance grows
Sharing a Pro mailbox doesn't divide its allowance between people. It grows by 1,000 for each person entitled on the mailbox.
A Pro mailbox has up to 1,000 MCP calls a day, counted over a rolling 24 hours. Shared, the allowance is 1,000 multiplied by 1 plus the number of people active on it. So a Pro mailbox shared with 2 people has 3,000 calls a day between the 3 of you. A parked or paused person doesn't count.
| Pro mailbox shared with | People, counting you | Calls a day |
|---|---|---|
| Nobody | 1 | Up to 1,000 |
| 1 person | 2 | Up to 2,000 |
| 2 people | 3 | Up to 3,000 |
| 4 people | 5 | Up to 5,000 |
-
Only a mailbox on Pro can be shared.
Sharing sits on top of Pro, and the panel says so if you try it on a mailbox that isn't.
If Pro lapses on a shared mailbox, the people stay attached. The mailbox drops to 5 calls a day between everybody on it, until Pro is bought again.
-
The smallest shared set-up comes to £154.98 + VAT a year.
That's one Pro mailbox and the Team 3 tier. Each further shared mailbox adds another Pro.
-
You can cap any one person lower.
A cap is a figure you set per person from the People tab. It applies on each mailbox they're on, as a second count inside the same check the mailbox's own limit uses.
-
Reaching a cap is a limit, not a fault.
A person who reaches theirs is told so in a sentence their assistant can relay: the mailbox itself still has capacity, and the owner can raise their ceiling from the People tab. The sentence says that it's a limit that was reached, not a fault.
New: routines
Email routines on a shared Pro mailbox
Routines come with the mailbox rather than the tier: its owner adds them from the mailbox's Routines tab, and they run in the owner's own Claude or ChatGPT. On a shared mailbox their calls come out of the allowance everybody on it shares, and since that grows with each person, a week of every routine is a smaller share of the week's allowance the more people there are.
-
A Pro mailbox, owner alone A week of all 5, against a week's 7,000
Up to 172 of 7,000
-
Shared with 2 people A week of all 5, against a week's 21,000
Up to 172 of 21,000
-
The owner sets them up
From the mailbox's Routines tab, and each one runs in the owner's own Claude or ChatGPT as a scheduled task, at the time they chose. Scheduled tasks in Claude need a paid Claude plan. On ChatGPT's free plan a task runs once a day, within a time window.
-
The drafts wait for the team
A Replies waiting routine saves its drafts in the mailbox's own Drafts folder, where whoever answers the mailbox finds them.
-
Its card says whether it ran
On the Routines tab, with when it ran and how many calls it made, and "Did not run" when a due run has not come.
On every mailbox of a Team account
The 6 claim and approval tools
Every mailbox on a Team account registers 6 tools that a mailbox on an account without a tier never sees.
They exist so that 2 colleagues, each with their own assistant, don't both answer the same message. And so that a person who may not send from the mailbox can still get a reply out, through you.
Claims: who is dealing with which message
claim_emailrelease_emailassign_email
-
Mark a message as being dealt with.
Claim a message, or a set of them, so colleagues sharing the mailbox know somebody's dealing with it, and nobody answers it twice. Hand a message to a named colleague, and release a claim when it's done.
-
Every listing says who holds what.
A reply, forward or draft reply to a message somebody else holds still does the work. It opens with one sentence naming them: information, not a refusal.
Approvals: a draft waits for the owner to send it
request_approvallist_pending_approvalsapprove_and_send
-
A draft can wait for the owner.
A person whose connection may draft but not send writes the reply as a real draft in Drafts, and marks it as waiting for the owner.
-
The owner's assistant lists what's waiting.
Every draft waiting, newest first, with who asked, when, the recipients, the subject and a preview.
-
Approving sends it the ordinary way.
One Sent copy, with the draft's own attachments and threading, and the draft removed from Drafts the way a mail client removes one it has sent. A draft nobody asked about is refused.
-
Changes go back by email.
Sending a draft back for changes is an ordinary email from the owner to the person. There's no tool for it.
Behind both: a keyword on the message, in your own mailbox
-
It lives on the message.
The mail server keeps it, so it survives the assistant, the session and the connection. It vanishes with the message if the message is deleted.
-
We record who, never what.
Who holds a message is a record of ours naming the mailbox, the folder, the message and the person. Never a subject, an address or a line of the message.
-
The keyword moves nothing, and marks nothing read.
Setting or clearing a claim, or a request for approval, leaves the message where it is, and doesn't mark it read.
-
Some mail servers can't keep a keyword.
A server that doesn't accept custom keywords is told so by the tools, rather than pretended at. And Outlook may not show a keyword it didn't set.
Each tool, with what it does and where it refuses, is on the tool reference. The Team Access guide walks through a claim and an approval end to end.
What you are told
The 2 owner alerts
Both are emails, and both are on unless you turn them off under what we email you about. Neither holds anything back.
They tell an owner what reading their own mailbox can't: the sends were made by somebody else, and the Sent folder doesn't say who.
- The Monday digest. Every Monday at 08:00 London time, an owner with somebody active on a mailbox gets one email: per person, the sends, filings and reads over the last 7 days, and the drafts waiting for approval across the shared mailboxes.
- The first-time-domain alert. The first time a shared person sends to a domain the account has not written to since Team Access began, through any mailbox, you are emailed once: who, which mailbox, the domain and the subject. Your own sends never alert; they only teach the account which domains it knows.
Out-of-hours alerts and behavioural alerts are deliberately not built.
Changing your mind
Upgrading, downgrading, cancelling and refunds
Up and down are immediate, and neither moves the date your year ends. Moving up invoices the difference for the rest of the year now, prorated by Stripe. Moving down credits the difference to your next invoice.
A downgrade names the people it affects first. The confirmation screen shows the direction and, on a downgrade, the people beyond the new allowance, newest first, before anything changes. They're parked, not deleted, and a bigger tier later seats them again, oldest first, without anybody being re-invited.
Cancelling is cancel-renewal. The seats run to the end of the paid year, and the tier ends on that day. Everybody on it is then parked: every call of theirs is refused until a tier is bought again.
Their levels, caps and connector URLs are kept, so buying a tier again restores them without re-inviting. Nothing is deleted.
A full refund of the year's Team payment ends the tier the same day. It cancels the subscription, parks everyone, and emails you naming them. A refund of only the prorated invoice for an upgrade changes nothing on its own.
The refunds and cancellation policy carries the 14-day right for UK consumers, and the cases we refund outside it, for a Team tier as for a Pro mailbox.
Questions
Questions about Team Access
What does a Team tier include, and what does it not include?
A tier is a number of named people, 3, 5 or 10. Each may get their own connection to any Pro mailbox you own, with their own connector URL, permission level, daily cap and line in the activity record. Every mailbox you share gets the claim and approval tools. A tier includes no mailbox: only a Pro mailbox, at £34.99 + VAT a year each, can be shared. One person on 3 of your mailboxes is one seat.
Do I still need Pro on each mailbox I share?
Yes. Team Access works on a mailbox on Pro. The control panel refuses an invitation naming one that isn't, with a sentence that names the mailbox and asks you to move it to Pro first, then invite. A shared Pro mailbox's allowance grows by 1,000 calls a day for each person entitled on it. If Pro lapses, the people stay attached and the mailbox drops to 5 calls a day between everybody, until Pro is bought again.
Can an invited person pass their invitation link to somebody else?
No. Only an account whose verified email address is the invited one can accept an invitation. Anybody else who opens the link is refused. The refusal names the account they're in and shows the invited address in masked form, so the mistake is visible without handing the address to whoever holds the link. Once accepted, the person is their account, whatever their address later becomes. Until then, the owner can resend, edit or withdraw the invitation at any time.
What happens if I downgrade with more people than the smaller tier allows?
The people beyond the new allowance are parked, newest first, and the confirmation screen names them before anything changes. A parked person's calls are refused, but nothing of theirs is deleted, and a bigger tier seats them again, oldest first, without re-inviting anybody. A downgrade credits the difference to your next invoice, and an upgrade invoices it now. Both are immediate, and neither moves the date your year ends.
What happens when I remove somebody?
Every share they held and every connection they made end in one action, and every connection ends on its next call: there is no session to wait out and nothing for them to sign out of. They are emailed to say so. An invitation that was never accepted is withdrawn without an email. Their lines in the activity record stay, so you can still see what was done and by whom.
What happens if I cancel a Team tier, or get it refunded?
Cancelling stops the renewal: the seats run to the end of the paid year and the tier ends on that day, when everybody is parked and kept rather than deleted. A full refund of the year's Team payment ends the tier the same day and parks everyone, and you are emailed naming them. Re-subscribing seats them again without re-inviting. The refunds page carries the 14-day right and the exceptions in full.
Invite the first person from the People tab.
Connect a mailbox, buy a tier on the Billing screen, and the invitation takes an address, a level and a cap. Nothing of yours is handed over.