- Help Center
- GitHub Integration Docs
- GitHub Connector
-
Get Started With Unito
-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Troubleshooting and FAQs
-
Data Privacy & Security
-
Integration Documentation
-
Atlassian Jira Integration Docs
-
Trello Power-Up Docs
-
2-Way ServiceNow Integration
-
Asana Integration Docs
-
Google Integration Docs
-
Salesforce Integration Docs
-
Wrike Integration Docs
-
Azure DevOps Integration Docs
-
Smartsheet Integration Docs
-
GitHub Integration Docs
What Permissions Are Required to Connect GitHub and Unito?
Setting up a GitHub flow through Unito requires you to be the owner of an organization. Here's more information to help you get set up.
Only GitHub organization owners can connect to Unito
To connect your GitHub organization to Unito and create flows, you must be the GitHub organization's owner. This ensures that only authorized individuals can grant Unito access to your organization's repositories.
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.
Repository Permissions:
In addition to organization owner access, you'll need the following permissions on the specific repositories you want to sync:
- Collaborator Access: This allows you to contribute to the repository and make changes.
- Repository Webhooks: Ensure the "repository webhooks for public and private repositories" permission is enabled for Unito to create webhooks, which are essential for real-time syncing. We do not require the admin:repo_hook permission.
You can get more information about these permissions here.
Note: We can't sync a repository if it was forked from another repository.