Concepts
What is Camper?
Camper keeps SaaS resources — groups, channels, teams, shared drives, calendars — aligned with your org chart and identity lifecycle.
When someone joins Engineering, moves to a new team, or leaves the company, Camper converges the memberships those org units grant on the apps you connected.
Who it is for
| Audience | Job |
|---|---|
| IT / identity operators | Connect the IdP, map structure, link resources, fix drift |
| Workers | Open My Access to see what access they should have |
Camper is not a VPN, not an IdP, and not a replacement for your HRIS. Your IdP remains the source of truth for people; Camper is the control plane for org-shaped access in other tools.
What Camper manages today
| App | Resources |
|---|---|
| Google Workspace | Groups, Shared Drives, Shared Calendars |
| Slack | Channels, User Groups |
| Atlassian | Teams |
| GitHub | Organization teams |
| Microsoft 365 (beta) | Teams (primary), private channels, standalone SharePoint, non-Team M365 Groups |
People always enter via SCIM from your identity provider — not by connecting those apps as “sources.”
Why not only IdP push groups?
Push groups are useful. Camper adds what operations teams still do by hand:
- Multi-axis org structure (department and teams and office, not one forced tree)
- Per-link policies (add-only channels, subtree coverage, pin exceptions)
- Managed lifecycle (create / archive) plus rename for any linked resource that follows org naming
- Dry run before first write
- Drift and dead-task queues when reality and desire disagree
- Worker pane of glass so employees can see expected access without admin tools
Deeper model: How Camper works.
Pricing in one line
One plan, banded by how many active identities your IdP syncs. Successful writes to connected systems use action credits; reads, dry runs, SCIM, and reconcile are free. Details: Pricing & usage.