Connections
Connections overview
Connections are installs of target providers. Camper seals credentials per tenant and runs health checks during connect.
| Provider | Auth model | Resources |
|---|---|---|
| Google Workspace | OAuth admin consent (SA advanced) | Groups, Shared Drives, Calendars |
| Slack | OAuth (workspace or Enterprise Grid) | Channels, User Groups |
| Jira / Atlassian | OAuth 3LO (API token advanced) | Teams |
| GitHub | GitHub App (preferred) or PAT | Teams (foundation) |
What is not a connection
- Directory / SCIM — identity source settings
- SSO — how operators and workers sign in
- Okta as a target — Okta is not provisioned by Camper
Connect flow pattern
- Open Connections in the admin app.
- Choose the provider → enter credentials (or complete OAuth).
- Camper seals secrets and runs provider health checks.
- Status becomes
activeorerrorwith diagnostic detail.
Request a connector
Missing an app? Use Request a connector on the Connections page. Requests are stored for the Camper product team (and show up in your Activity feed). New connectors are planned OAuth-first.
Backlog examples: Microsoft 365, 1Password, OpsLevel, and other tools where group membership is painful to maintain by hand.
Provider-specific setup: