CamperDocs
Open app

Operators

Link resources

Resources are the groups, channels, teams, drives, and calendars Camper keeps aligned with your org chart. Operators attach them under Resources → Link resource.

Wizard flow

Linking is a short step-by-step flow (same pattern as Setup):

  1. Where — Create new (managed) vs attach an existing app object, and pick the org unit.
  2. App — Choose an active connection (Google, Slack, Jira, GitHub).
  3. Type — What to manage (group, channel, team, …). Options depend on the app.
  4. Details — Display name, naming rules, and (for attach) which downstream object.
  5. Access — Who gets in, role, what happens when people leave, outsiders.
  6. Review — Dry-run membership diff; nothing goes live until you confirm.

Editing an existing link starts on Details. App and type stay locked; org unit, naming, and access rules can still change.

Managed vs attached

ModeWhat Camper owns
Create new (managed)Creates the object (when supported), renames from a template if you opt in, and drives membership
Attach existingMembership only — does not take rename ownership of the app object

When attaching, Camper can browse and search live resources (Google, Slack, Jira). Paste an id if listing isn’t available (e.g. some GitHub cases).

Naming

For managed resources:

  • Follow org renames — Use a template such as {{org_unit.name}} Team so renames stay in sync with the org unit.
  • Keep a fixed name — Never auto-rename when the org unit changes (exclude from rename fan-out).

Access rules (plain language)

These map to engine fields; the UI avoids jargon.

SettingMeaning
Who should get access?Only this org unit vs this unit and everything under it (children teams, etc.)
Access level in the appMember (usual) or Owner when the provider supports elevated roles
When someone leaves or is suspendedRemove them promptly, or keep until deprovisioned (rare)
People added outside CamperReport only (recommended) as drift, or remove outsiders so Camper enforces the desired set strictly

Unmatched downstream members are drift by default, not silent deletes — “remove outsiders” is intentional and shown as a warning on review.

Dry-run before go-live

Every create and edit ends on Review. Camper computes desired membership and shows adds/removes before anything is written. Confirming updates the link; the worker applies membership ops on the next reconcile.

Related