29-May-2026 — Setting up a Gmail inbox for committee replies


Why each group sets this up themselves

Every group runs through these steps on its own Google account. There is no shared central project that all groups plug into — each group creates its own Google Cloud project, its own OAuth client, and its own dedicated service Gmail account(s) for the role mailboxes. The steps below describe one group's setup; another group repeats the whole thing independently.

This is deliberate, and it saves real money. Reading the contents of a Gmail mailbox uses what Google calls a restricted scope. For an app that's published to the public, Google requires a third-party security audit called CASA before it will allow that scope — roughly £400–£1,200, repeated every year or two. We avoid that entirely, and the way we avoid it is precisely because each group is self-contained:

Google assesses CASA per OAuth client. Because each group's client is its own little self-contained setup — one owner authorising their own service mailboxes, never published — the audit requirement simply never triggers. If we instead ran one central client that lots of different people connected their personal Gmail accounts to, that would trip the requirement and we'd be back to paying for verification.

What this means in practice

Back to main article