Every repo, team and outside collaborator, owned
Org roles, team membership and repo permissions, including the outside collaborators nobody remembers inviting.
Ploy connects to a GitHub organisation through a GitHub App, so access is scoped to the org you install it on and can be revoked from GitHub at any time.
What Ploy reads
- Organisation members and GitHub Enterprise users
- Teams and team membership
- Repositories, and the collaborators on them with their permission level
- Enterprise licence and owner grants, where the install reaches the enterprise
What Ploy can change
Revoking a grant removes the user from the org, the team, or the repository, depending on which level the grant was issued at. Ploy can also invite someone into the organisation and withdraw an invitation that was never accepted. It never creates or deletes a personal GitHub account.
Setting it up
Install the Ploy GitHub App from your organisation settings and approve the requested read scopes. The first sync usually completes in under a minute.
Three jobs this connector does on day one
The access nobody remembers granting
Repository collaborators are read alongside organisation and team membership, so someone added to a single repo two years ago sits on the same list as everyone else.
Teams and repos are the grant
An approved request writes organisation, team or repository collaborator access straight into GitHub, and takes it back when the grant ends.
Off the organisation, invitations included
On the last working day Ploy removes the person from the organisation, its teams and the repositories they collaborated on, and withdraws any invitation still pending.
