Directory
Google Workspace setup
Google Workspace has no native SCIM client — it can't push users into a SCIM endpoint the way Okta or Entra ID can. Two supported paths:
Path A (recommended today): front Google with an IdP that speaks SCIM
If Google Workspace is your identity source but you also run Okta, Entra ID, JumpCloud, or OneLogin in front of it, provision Camper from that IdP instead — see the Okta or Entra ID guides. Google stays the mail/calendar system; the IdP owns provisioning.
Path B: sync via a SCIM bridge
Any SCIM 2.0-capable provisioning tool that reads the Google Directory API can push into Camper's endpoint (Base URL + bearer token from Settings → Identity Providers). Point the bridge at:
POST/PATCH /scim/v2/Users— identities,activeflag,rolesPOST/PATCH /scim/v2/Groups— Google groups → Camper team units
Map Google's orgUnitPath or custom schema fields onto the profile attributes
your Camper Attribute map expects, so people land on the hierarchy.
Direction
A first-party Google Workspace directory integration (OAuth against the Directory API with webhook user updates and selective group/OU sync — scoping which groups and OUs sync, children included) is on the roadmap as part of multi-IdP directory sources. Until then, Google Workspace remains fully supported as a target (Groups, Shared Drives, Calendars) via Connections — that is separate from the directory and unaffected.
Don't confuse source and target
| Role | Where it's configured | What it does |
|---|---|---|
| Directory source | Settings → Identity Providers (SCIM) | Who exists, org placement, operator roles |
| Provisioning target | Connections → Google Workspace | Groups/Drives/Calendars Camper manages |
Connecting Google under Connections does not import people — the directory always comes from SCIM.