How it works

Data flows one way: from the upstream directory into Rolodex, and from Rolodex out to the systems that ask. Here is the whole loop.

Step 1
Configure a sync source
An admin adds an AD/LDAP sync source to an Org: the server URL, the base DN, the bind DN and optional user and group filters.
Step 2
Sync runs fill the directory
Each sync run upserts users and groups and tombstones users who are gone. A scheduled drain or an admin starts the run.
Step 3
Publish what should be public
Every row starts private. An admin publishes a user or group, and only then does it appear on the public surface, without personal fields.
Step 4
Look people up
Signed-in people search users and groups in the web app or call the LDAP Sync Cache lookups. Tools fetch SSH keys by user or group name.
Step 5
Bind groups to access
Bind a directory group to a team, repo, project or group path on GitHub, Azure DevOps or GitLab, preview the grants, then confirm.
Step 6
Hear about changes
Register a webhook endpoint and verify the X-Rolodex-Signature header on each delivery of an event.

Look up anyone in your directory