Careers and workplace integration · Updated November 15, 2026

Google Workspace integration

We set up Google sign-in for staff, limited to your Workspace domain, and feed Sheets, Calendar and Drive content into your pages. Both work on WordPress, Astro, Next.js and custom software. Webflow sites get the feeds only.

Rated 5.0 out of 5,72 Google reviews

Google Workspace at a glance

Connects
Sign in with Google (OpenID Connect), the Sheets, Calendar and Drive APIs, and publish-to-web embeds.
WordPress
Google sign-in plugins with a domain allowlist; feeds through a plugin or a small one we write.
Webflow
Calendar and Sheets embeds, or a scheduled copy into the CMS. Google sign-in needs a separate app.
Astro or Next.js with Sanity
Auth.js Google sign-in with a hosted-domain check; server routes read Sheets and Calendar.
Custom software
Service accounts for shared files, OAuth for user data, domain-wide delegation only as a last resort.
Complexity
Low for embeds. Medium for sign-in and API feeds that need admin settings.
Typical setup
1 day for embeds, 2 to 4 days for domain-restricted sign-in, 4 to 10 days for API feeds.

How we connect Google Workspace

  • WordPress

    rtCamp's Log in with Google plugin limits sign-in and account creation to the email domains you list. Its page doesn't say it checks Google's hosted-domain claim, which Google says a server must verify, so for an intranet we review that or add the check ourselves. Sheets tables can come from a plugin such as FlexTable, which reads a publicly available sheet.

  • Webflow

    Calendar's embed code goes in an Embed element, and a published sheet can sit in an iframe. For events or tables styled like your site, we run a scheduled job that copies Sheets rows or Calendar events into Webflow CMS items. Since Webflow retired User Accounts on January 29, 2026, Google sign-in has nothing to attach to there, so staff pages run in a separate app.

  • Astro or Next.js with Sanity

    Auth.js's Google provider handles sign-in on the server. We send the hd parameter to skip the account picker, then reject any ID token whose hd claim isn't your domain. Sheets and Calendar reads happen server side and are cached, and editors arrange them in Sanity.

  • Custom software

    Shared data, like an events calendar or a directory sheet, is shared with a service account so it reads only those files. Google advises domain-wide delegation only when direct access or user consent can't do the job, with the fewest scopes and no key files. A super administrator grants it in the Admin console.

What organizations use Google Workspace for

  • Staff-only pages with Google sign-in

    With the OAuth app set to Internal, only people in your Google Workspace organization can authorize it, and Google's verification review doesn't apply. The Google Cloud project has to sit inside your organization.

  • Events from Google Calendar

    A public calendar embeds with Google's code, at least 500 pixels wide and tall. For events shown as your own cards, we read the Calendar API, which allows 10,000 requests a minute per project and 600 per user as of November 15, 2026. Your admin's external sharing setting decides whether event details can be public at all.

  • Lists and tables from Sheets

    Program lists, locations and other staff-maintained tables can live in a sheet. The Sheets API allows 300 read requests a minute per project and 60 per user, so we read once, cache, and refresh on a schedule. A sheet that outgrows that moves to a database or the CMS.

What to watch out for

  • Limits of publish to the web

    A published sheet is read-only but open to anyone with the URL, unless a Workspace account limits it to your organization. Changes take a few minutes to appear, and your admin may have turned publishing off. We publish only the tabs the site needs, and never a sheet holding personal information.

  • No Canadian data region

    As of November 15, 2026, Workspace data regions offer the United States, Europe or no preference, and data region policies need editions such as Enterprise Plus or Frontline Plus. Google also offers local data storage, a copy kept in a country you choose; its pages don't list countries, so ask Google about Canada.

  • Domain-wide delegation

    A service account with domain-wide delegation can act as any user in your domain within its scopes. When we can't avoid it, we keep the account in its own Google Cloud project with read-only scopes. If a plugin asks for delegation, treat it as a request for every user's data in those scopes.

Questions about Google Workspace

Is the hd parameter enough to keep outsiders out?

No. Google calls it a UI hint that a visitor can edit. Your server has to read the hd claim in the signed ID token and refuse anything that doesn't match your domain. We build that check into every Google sign-in.

Do we need an Enterprise edition for this?

Not for sign-in or the Sheets, Calendar and Drive feeds. Your edition matters if you need data region policies, so check it if residency is a requirement.

What about privacy law?

Sheets feeding a public page shouldn't hold names, emails or phone numbers unless those people agreed to be listed. Name Google and your site's host in your privacy notice. With no Canadian data region, Quebec staff data in Workspace may be stored outside the province, and Law 25 calls for an assessment before that.

Feeding your site from Google Workspace?

Tell us which sheets, calendars or folders hold the content and who needs to sign in. We'll say what can be embedded, what needs the API and what your Workspace admin must allow.

Book a call