GitLab groups and who is in them, reconciled every sync

Group membership and the GitLab role behind it, reconciled on every sync.

Book a demo

TYPE · SAASAUTH · OAUTHDOMAIN · GITLAB.COM

GitLab connectorHOURLY SYNCCAPABILITIES

WHAT PLOY DOES

Sync GitLab usersEvery user in the GitLab organisation arrives in Ploy as an identity.

READ

Read account status and last activityWhether an account is active or blocked, and when it was last used.

READ

Discover groupsGitLab groups come in as resources and are reconciled on every sync, so a group deleted in GitLab is archived in Ploy. Projects are not read.

READ

Read group membership and rolesWho is in each group and at which GitLab role, held as the entitlement. Blocked members are left out of the list, so their group access drops in Ploy.

READ

Register GitLab as an app in useGitLab lands in the app inventory with its account holders attached. Third party apps are not discovered through it.

READ

2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

GROUPS

Who is in which group, and at what role

Group membership arrives with the GitLab role attached, so Owner and Maintainer read as entitlements rather than sitting in a settings page nobody opens.

REVIEWS

A campaign that knows about GitLab

GitLab group access sits in the same review as the rest of the estate, with last activity beside each member so a reviewer can see who is still using it.

LEAVERS

Blocked in GitLab, gone from the record

The leaver run flags the GitLab account and the groups it belongs to. Once the account is blocked, it drops out of the membership list at the next sync and the access Ploy holds matches GitLab again.

2.3