Directory
Google Workspace setup
Google Workspace has no native SCIM client — it cannot push users into a SCIM endpoint the way Okta or Entra ID can. Two supported paths cover directory today.
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 (or a bridge that speaks SCIM).
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, OneLogin, or similar in front of it, provision Camper from that IdP:
Google stays mail and calendar; 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).
Map Google’s orgUnitPath or custom schema fields onto SCIM attributes so people land on an axis. orgUnitPath (/Corporate/TechOps) maps neatly onto one axis with delimiter /. Attribute rules: Custom attributes → Google Workspace.
Direction
A first-party Google Workspace directory integration (Directory API + selective OU/group sync) is on the product roadmap. Until then, Google Workspace remains fully supported as a target via Connections.