Documentation
Camper is an automated organization-resources control plane for IT. When people join, move, or leave — and when org units change — Camper converges membership on Google Workspace, Slack, Jira, and GitHub.
This site is product documentation for operators: directory setup, connections, and day-to-day use.
Start here
| Guide | Description |
|---|---|
| What is Camper? | Control loop, targets vs directory |
| Identity & directory | SCIM-first multi-IdP, roles, My Access |
| Connections | Google, Slack, Jira, GitHub |
| Setup wizard | First-run path for a new tenant |
Product principles
- Directory is not a target — people arrive via SCIM from your IdP; Connections are only downstream apps.
- One SCIM User — always a workforce identity; SCIM
roleselevate operators (e.g. Admin). - Tenant-defined org — map attributes and groups into your hierarchy; do not hardcode one HRIS shape.
- Engine owns membership — connectors execute idempotent ops; mass-removal guardrails apply.
Get started
Quick start
Get a tenant ready for directory and app connections.
Get started
Setup wizard
Guided first-run — Directory, mapping, targets, reconcile.
Get started
About these docs
What this site covers and how to get help.
Concepts
What is Camper?
Control loop that keeps targets aligned with org structure.
Directory
Identity & directory
SCIM-first multi-IdP directory, roles, and My Access.
Directory
SCIM provisioning
How IdPs push users and groups into Camper.