Connections
Connections overview
Connections are installs of target providers — the apps Camper writes membership into. Credentials are sealed per workspace. Health checks run during connect and again on an ongoing basis.
Supported providers
| Provider | How you connect | Resources |
|---|---|---|
| Google Workspace | Workspace admin signs in with Google | Groups, Shared Drives, Calendars |
| Slack | Workspace or Enterprise Grid install | Channels, User Groups |
| Atlassian | Org admin email + classic API token | Teams |
| GitHub | GitHub App on an Organization | Teams |
| Microsoft 365 · beta | Entra admin consent (app-only Graph) | Teams, private channels, SharePoint sites, non-Team M365 Groups |
Every tile is the same compact card: provider, what Camper manages, a status chip, one line of context, and one button. Set up opens a guided dialog; once connected the tile offers Manage.
What is not a connection
| Not here | Where it lives |
|---|---|
| Directory / SCIM | Settings → Identity Providers |
| SSO | Same settings page — how people sign in |
| Okta / Entra as targets | Camper does not provision into the IdP |
A banner on Connections points back to Identity Providers when the directory is not set up yet.
Connect flow pattern
Every connector follows the same dialog so the second app works like the first:
- Open Connections → Set up on a provider.
- Check access — which admin role you need, what Camper will and will not ask for.
- Grant access — OAuth consent or credentials. Optional advanced credential paths sit behind a disclosure.
- Done — secrets sealed, health checks run, confirmation with a link to the next move.
Providers that redirect out for consent bring you back into the dialog on the step that completed — success on Done, or the failing step with the reason. Status becomes active or error either way.
Manage a live connection
Manage shows what Camper is talking to (organization, domain, credential kind, last health check), reconnects or rotates credentials by re-running setup, and removes the connection.
Remove a connection
Remove connection clears sealed credentials and marks the install revoked. Linked resources stay in Camper so you can re-attach after reinstall — they are not deleted automatically.
GitHub: organizations only
Install the Camper GitHub App on a GitHub Organization. Personal accounts cannot host org teams; if you pick a personal account, Camper shows a warning and does not leave a failed connection behind.
Link existing resources
On Resources → Link resources, pick Link existing, then the app. Camper browses and searches live resources from Google, Slack, Atlassian, GitHub, and Microsoft 365 across every type that app supports, ranked against the org unit name. Tick as many as you want — they all go in one batch. Paste an id remains available as a fallback. Full flow: Link resources.
Request a connector
Missing an app? Use Request a connector on the Connections page. Requests are stored for the Camper product team and appear in your Activity feed. New connectors are planned OAuth-first.