Directory
Org catalog
The org catalog is the single pane of glass for org structure. Open Catalog in the sidebar. One table per axis lists every unit with the facts you need day to day:
| Column | What it tells you |
|---|---|
| Name | The unit, indented under its parent when the axis nests |
| People | Active identities in this unit and everything below it |
| Resources | Downstream groups, channels, drives, and teams linked to it |
| Metadata | One column per attribute the axis defines |
Every name and resource chip is a link, so you can go from a unit to a Slack channel and back without leaving the catalog.
For a picture of “if I change this team, what moves?” see Catalog graph.
Axes on the catalog
Each axis is a tab when you have more than one. On the active axis:
- Edit axis — rename, source attribute, membership, metadata definitions
- Delete — remove the axis (cascade confirmation if units remain)
- New axis / New org unit — create structure without waiting on SCIM
Full multi-axis drafts and placement preview: Settings → Mappings.
Creating units
Two paths that converge on the same unit:
- Create first. New org unit makes an imported unit immediately — pick axis, name, optional parent, metadata. You can link resources right away. If the IdP later sends a matching attribute value, people land on that unit instead of a duplicate.
- Let sync suggest. New attribute values and IdP groups appear as Suggested. Import the ones you manage; ignore the noise.
Filter to Suggested, select several, then Import selected, Import with children, or Ignore. When nobody active maps to a suggested unit anymore, Camper drops that suggestion.
Only imported units can hold resource links.
Unit detail
Opening a unit shows:
- Where people come from (axis and attribute value)
- People currently placed, including nested counts
- Every linked resource with policy summary and drift state
- Metadata values (editable inline)
- Rename — updates the name used to match directory attributes. Linked resources that follow org names rename on the next reconcile. If the directory already created a sibling unit, use Treat as rename instead.
- Treat as rename — when people vanished from this unit onto a sibling (typical HRIS department rename). Moves linked resources onto the surviving unit. Camper asks before doing this; a real team transfer looks the same.
- Not a rename — hides that suggestion when people really moved. The empty unit keeps its links. Treat as rename is still on the unit if you change your mind.
- For suggested units: Import / Ignore
- Link resources — opens the link panel with the unit already fixed
- Link resources — opens the link panel with this unit fixed. Find matches across apps ranks unlinked groups, channels, and teams whose names resemble the unit; tick as many as you want, set the rules once, and review one dry-run for the batch.
- Unlink on a linked resource — Camper stops using this unit for membership. The object stays in Camper and in the app; people already there stay.
Metadata attributes
Attributes are defined on the axis and typed so every unit on that axis has the same shape:
| Type | Good for |
|---|---|
| Text | A Jira team id, PagerDuty service id, internal code |
| Number | Cost center |
| URL | Team wiki or runbook |
| Distribution list or shared mailbox |
Values are set per unit. They also appear read-only on a linked resource. Removing an attribute from an axis hides its column; stored values remain if you re-add the attribute later.