Directory
Identity & directory
Camper’s workforce directory is IdP-sourced and multi-vendor via standards — not an Okta-only API connector as the product path.
SCIM-first
Your IdP (Okta, Entra, and other SCIM-capable systems) pushes Users and Groups to Camper:
- Users →
identities(email, status, full attribute bag) - Groups → multi-axis membership (e.g. Teams)
- Arbitrary attributes → mapped into your hierarchy levels
HRIS tools (e.g. Rippling) should feed the IdP; Camper does not require a direct HRIS integration.
Roles → operators
Every SCIM User is a workforce identity.
If the User includes a multi-value roles attribute with an operator role (for example Admin), Camper also grants dashboard operator access (RBAC). Users without operator roles remain directory members and use My Access.
SCIM roles | Product experience |
|---|---|
| includes operator role (e.g. Admin) | Full admin UI (Connections, links, drift) |
| no operator role | Platform viewer + My Access |
Active SCIM Users always receive a platform account (viewer unless elevated). Authentication (SSO / OTP / passkeys) is separate from directory provisioning — prefer SCIM so people and roles exist before first login.
Directory settings vs Connections
| Surface | Purpose |
|---|---|
| Directory settings | SCIM base URL, bearer token, attribute/group maps |
| Connections | Target apps only: Google, Slack, Jira, GitHub |
Do not treat Okta as a peer of Slack on the Connections page.
Org placement
- Define hierarchy levels for your tenant (not a fixed Rippling four-level enum).
- Map profile attributes → hierarchy leaf.
- Map SCIM Groups → team / multi-axis units.
- Org units can also be created manually.