What this article covers:

  • GitHub permissions required to use Unito

GitHub permissions required to use Unito

You need to both be a member of the organization that owns the repository you want to sync and a collaborator (which is different from a contributor). If your organization has enabled third-party application restrictions, you'll need to follow this step-by-step guide for approving third-party apps in GitHub.

In addition, we need the repository permission that includes ‚Äúrepository webhooks for public and private repositories‚ÄĚ to create webhooks. We do not require the admin:repo_hook permission. You can get more information about these permissions here.

Most importantly, Unito will never ask for, or require access to, any code you have stored on GitHub.

Note: We can't sync a repository if it was forked from another repository.

OAuth Scopes

Repository Permissions

Read

Metadata

Search repositories, list collaborators, and access repository metadata.

Read & Write

Pull requests

Pull requests and related comments, assignees, labels, milestones, and merges.

Read & Write

Webhooks

Manage the post-receive hooks for a repository.

Read & Write

Projects

Manage repository projects, columns, and cards.

Organization Permissions

Read

Members

Organization members and teams.

Read & Write

Webhooks

Manage the post-receive hooks for an organization.

Read & Write

Projects

Manage organization projects, columns, and cards.

User Permissions

Read

Email Address

Manage a user's email addresses.

What's next?

Learn how to set up your first flow.
Learn how to sync priorities and importance.
Not a Unito user? Try Unito for two weeks free!
Already a user? Sign in here!

Did this answer your question?