Concepts
What is Camper?
Camper keeps SaaS resources (groups, channels, teams, drives, calendars) aligned with your org chart and identity lifecycle.
Control loop
- Ingest — Customer IdP pushes people and groups via SCIM into Camper’s directory.
- Desire — Active identities × resource links (and pins) produce desired memberships.
- Observe — Target connectors list actual members.
- Converge — Diff + safety guardrails → provisioning tasks per provider.
Unlike IdP push groups alone, Camper can also create, rename, and archive managed resources when org units change.
Two planes
| Plane | What | UI |
|---|---|---|
| Directory | Who exists; org placement; operator roles | Settings → Directory (SCIM) |
| Targets | Google / Slack / Jira / GitHub installs | Connections |
See Identity & directory for SCIM, roles, and My Access.
Org units and links
- Org units are tenant-defined (hierarchy + optional multi-axis teams).
- A resource link binds an org unit to a downstream resource with membership policy (direct/subtree), removal policy (sync vs retain), and optional naming templates for managed resources.
Deep semantics: engineering domain model in the repo.