Integrations
Integrations
Data comes into Rolodex from one place, the upstream directory, and goes out as lookups and as access on other platforms. These pages say which way each one flows.
- 01
Active Directory / LDAP
Sync source: feeds the directory. The one real sync source. Rolodex reads users and groups from an LDAP server and keeps them in its cache.
- 02
GitHub
Access target: team membership and repo collaborators. Directory group membership becomes GitHub team membership or repo collaborator access through an access binding.
- 03
Azure DevOps
Access target: project team membership. Directory group membership becomes membership of a team in an Azure DevOps project.
- 04
GitLab
Access target: group and project membership. Directory group membership becomes membership of a GitLab group or project, at an access level.
- 05
Fleetworks apps
Access target: role claims for suite apps. Rolodex can write the Fleetworks role claim onto a person’s account in a Fleetworks app, from group membership.
- 06
Zitadel sign-in
Identity provider and reconciliation source. People sign in through the shared Fleetworks Zitadel instance with OpenID Connect; Rolodex also reads Zitadel accounts to link them to directory users.
- 07
Yellow Pages
Loose pointer to the service catalog. A directory user or group can carry a YellowPages service ID that points at a service in the Fleetworks catalog.