🟢 Google Workspace integration

If your school runs on Google Workspace (or Google Workspace for Education), this is usually the simplest way to onboard your staff to TSNC. One click to authorize, map your organizational units to TSNC roles, hit Sync, and you’re done.

What you’ll get

  • Staff auto-imported from your Google directory. No CSV exports.
  • OU-based mapping. Your “Staff” OU becomes TSNC staff; “Teachers” becomes TSNC teachers; whatever structure you already have, you map it.
  • Sync on demand. Click Sync Now any time. New hires get pulled in; suspended users get deactivated.
  • SSO support comes free. The same Google accounts can sign in to TSNC via “Sign in with Google.”
💡
Best for
Schools where everyone already has a @yourschool.org Google account and you take attendance / send email / share docs through Workspace.

Before you start

  • You’ll need to be a Google Workspace Super Admin for your domain. A delegated admin without the right role bundle will fail at the consent step.
  • If you’re on Google Workspace for Education with under-18 users in scope, the consent step may be blocked by Google’s age-based access settings. See the Trust TSNC in Workspace for Education guide for the 5-minute fix.
  • Your staff OU structure should be tidy. If “all employees” live in one OU you’ll do one mapping; if you split staff/teachers/parents, you can map each separately.

Step-by-step setup

  1. 1
    Open the Integrations page

    In TSNC, head to Admin → Integrations. The Google Workspace card is the first one on the page.

  2. 2
    Click Connect Google Workspace

    You’ll be redirected to Google’s consent screen. Sign in as your Super Admin if you aren’t already. Google will ask you to authorize TSNC to read your directory — specifically the Admin SDK’s read-only scopes for users, groups, and organizational units. We never request write access.

  3. 3
    Approve the consent

    After clicking Allow, Google redirects you back to TSNC. You should see a green “Connected” state on the Google Workspace card showing your domain (e.g. stmarys.edu).

    ⚠️
    If you see “Error 400: access_not_configured”
    That means your Workspace for Education tenant is blocking unconfigured third-party apps. The fix is in the Trust TSNC in Workspace for Education guide — it takes about 5 minutes.
  4. 4
    Map your OUs

    Click Configure OU mappings. TSNC will fetch the list of organizational units from your directory and show them all. For each OU you want to import, set:

    • Account type — Staff or Student. Students are not pulled into the staff roster but ARE tracked separately if you have the student rostering feature enabled.
    • Department (optional) — appears in TSNC reports and can be used to scope campaigns.
    • Enabled — toggle off to temporarily exclude an OU without deleting the mapping.

    Sensible defaults: if your OUs are named “/Staff” and “/Students,” map them as such. If you’ve subdivided by building or grade, you can either map each leaf OU individually or map the parent and let TSNC inherit.

  5. 5
    Save mappings & sync

    Click Save mappings then Sync Now. Sync runs in the background; refresh in 10-30 seconds to see the user counts. Your staff roster page should now show the imported users.

  6. 6
    Done

    You can re-sync at any time. There’s no scheduled sync yet — we’ll add cron-style daily sync once we know how stable the integration is for your school. Meanwhile, you’ll want to click Sync Now any time you have major staff changes (start of school year, mid-year hires, departures).

What syncs (and what doesn’t)

Per user we sync:

  • Email address — primary email from Google.
  • First and last name — from Google profile.
  • OU membership — drives which TSNC mapping applies.
  • Suspended status — suspended Google users are skipped (and deactivated in TSNC if previously synced).

We do NOT sync:

  • Phone numbers, addresses, photos, custom Google profile fields.
  • Group memberships beyond OU.
  • Calendar, Gmail, Drive, or any user-content data.

Sender address check

Once a day, separately from the staff sync, we read every address in your Google directory — every person’s account (staff and students, suspended accounts too), their aliases, and your groups and group aliases — and keep only a one-way keyed fingerprint of each. A fingerprint cannot be turned back into an address, and nothing we keep marks which addresses are students’. We store no address, no name, no OU and no account details — only the fingerprint and whether it is a person’s address or a group’s. This read never creates, invites or changes anyone, and it ignores which OUs you chose to sync.

When mail claims to come from your own domain but from an address that is not in the index, we hold that address for at most a day while we check it with Google, then delete it. We keep only its fingerprint and Google’s answer, for 7 days. Only if Google confirms the address does not exist do we stop treating the message as internal mail: it no longer gets the internal-sender trust boost, and it can’t show green. That is how an attacker’s made-up “support@yourschool” address loses the trust your real addresses earn. This applies to Mobile Coverage banners, the Outlook add-in and the Chrome extension (version 1.9.153 and later, for staff accounts). If a legitimate system sends from an address that isn’t a real mailbox (a student information system’s no-reply address, for example), add that address to your safe senders. With Mobile Coverage, a system like that is also recognized on its own once it has been sending to your school for at least two weeks (three or more messages) and its mail passes your domain’s DMARC check.

The Integrations card shows how many addresses are indexed and when the last full read finished. If it says it is not flagging anything, it also says why. The most common reason is that the admin who connected Google cannot read groups: without that, we cannot confirm that an address does not exist, so nothing is flagged. A Google rate limit only cuts one day’s read short; the last full read keeps working for up to 3 days, and the next daily read tries again. A directory with more than 200,000 accounts or more than 80,000 groups is too large to index yet. The card says so and names the limit it hit. We stop using the index within five minutes, and within about ten minutes we delete every fingerprint and every stored answer for it; an address still waiting to be checked is deleted without being checked. While it stays too large we keep no addresses and no address fingerprints for it, only the number of accounts and groups we counted.

Disconnecting

Click Disconnect on the Google Workspace card. This revokes TSNC’s OAuth refresh token on our side. Your previously-synced staff stay in your TSNC roster — disconnecting stops future syncs but doesn’t delete them. Run the disconnect, then decide what to do with the existing staff records (keep them, deactivate by hand, etc.). The sender-address fingerprints are deleted when you disconnect.

For full revocation on Google’s side, your admins can also visit myaccount.google.com/permissions and remove ThouShaltNotClick from the authorized apps list.

Common questions

Does this give TSNC access to my staff’s email or files?+

No. We only request read-only scopes for the Admin SDK directory — users, groups, organizational units (the group scope is what lets the sender address check recognize your group addresses). We never see message content, file content, calendar data, or any user-private information.

Does the staff member need to do anything?+

No. The integration runs in the background using your admin authorization. Staff just need to know their email + Google password (or the SSO flow if you’ve enabled “Sign in with Google” for TSNC). If a teacher tries to sign in to TSNC and gets an “error_400 admin_policy_enforced” message, see the Trust TSNC guide.

What if I have a multi-domain Workspace tenant?+

TSNC syncs based on the primary domain associated with the OAuth grant. Multi-domain tenants are supported but we sync from the customer-level directory (across all domains). If you only want to import staff from one specific domain, scope by OU instead.

Can I have both Google Workspace AND a SIS integration active at once?+

Technically yes, but it’s usually not necessary. If your SIS and Google directory have the same staff list, Google Workspace is simpler. If your SIS has staff that aren’t in Google (or vice-versa), pick whichever has the more authoritative list. Running both means you’ll see duplicate-account warnings.

What if sync removes someone I want to keep?+

Deactivation isn’t deletion — the user is marked inactive and their TSNC data (training progress, phishing-sim results) is retained. If a deactivation was wrong, re-activate them via the Staff page; the next sync will leave them alone as long as they’re back to active in your Google directory.

How long does the sync take?+

Typically 5-30 seconds for a school under 200 staff. Larger tenants (1000+ staff) can take 1-2 minutes. The page polls automatically — you don’t need to hit refresh.

← Previous
All integrations
Next →
Clever integration