Directory
Org unit leads
A lead is someone who oversees an org unit (for example a product team). Leads are set in Camper on the unit itself — not from SCIM, and not the same as a Camper dashboard admin.
Why leads exist
Almost every team has people who should get more permission on the team’s resources than a regular member — without becoming full owners that leave broken last-owner situations when someone leaves the company.
Camper elevates leads only where the target app has a safe intermediate role below owner.
What elevated access means
| Linked resource | Regular members | Leads |
|---|---|---|
| Google Group | Member | Manager (not Owner) |
| Google Shared Drive | Contributor | Content manager (not Manager) |
| Shared calendar, Slack, Atlassian teams, GitHub teams, Microsoft 365 (Team, private channel, SharePoint, group) | Same as members | Same as members |
On apps with only member vs owner (or flat membership), leads still appear as ordinary members when the unit is linked. Camper does not auto-promote anyone to provider owner via leads.
How to set leads
- Open Catalog and the org unit (team or department).
- In the Leads card, Add lead and search the directory.
- Linked resources update on the next reconcile.
You can add several leads. Removing a lead demotes them on elevating resources if they still belong to the unit as a normal member.
Leads vs pins
| Leads | Pins | |
|---|---|---|
| Where | On the org unit | On a resource |
| Purpose | Oversight / elevated access | Exception membership (include someone outside the unit) |
| Role | Elevated where supported | Always the same as ordinary members |