What this article covers:
Required permissions for each integration
OAuth Scopes info for each integration
In order to sync the things you care about, Unito needs the authorization to make changes within your tools. For most tools, the authorization process is fairly simple. However, there are some permissions you should check so we can sync without issues. Here are these permissions, outlined for each tool.
Trello
Just make sure the user account selected for the flow is a member of the Trello Board you want to sync.
OAuth Scopes
Read | reading of boards, organizations, etc. on behalf of the user |
Write | writing of boards, organizations, etc. on behalf of the user |
Account | read member email, writing of member info, and marking notifications read |
Jira
In order to sync your Jira projects, you'll need a mix of global and project-specific permissions, from login permissions to issue and comment permissions. You can find the full list of user permissions here.
If you get stuck on setting up permissions schemes in Jira, you can find a guide here.
OAuth Scopes
Read | View, browse, and read information from Jira. |
Write | Create or edit content in Jira, but not delete content. |
Asana
Your account needs to be a full member of your organization, not a guest. Then, make sure the account is part of the Asana team that owns the project you want to sync.
OAuth Scopes
Default | Provides access to all endpoints documented in our API reference. |
Teamwork
In order to properly sync tasks, Unito users need to be a Client User in Teamwork and not just a Collaborator.
Beyond that, Unito only needs special permissions if you want to create Teamwork projects directly from Unito. To do this, you must have administrator permissions in Teamwork or permission to add projects. If you don't have these permissions, reach out to someone who has administrator permissions.
GitHub
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. |
Zendesk
Confirm that your Zendesk account has admin privileges. We need this in order to search for certain endpoints and create webhooks.
OAuth Scopes
Read | gives an app read access to all resources (tickets, users, auditlogs - read only, organizations, hc, apps, triggers, automations, targets) |
Wrike
Make sure the project or folder is shared with the account you're using for your workflows. Also, because all projects and folders in Wrike are private by default, the ones you want to sync need to be shared with the account used to sync them.
HubSpot
All you need is to make sure you're a member of the HubSpot account that needs syncing.
OAuth Scopes
Contacts | Provides access to Contact, Companies, Deals, Properties, Engagements, and Owners endpoints |
GitLab
The GitLab account you use with Unito needs to be a member of the organization that owns the repository that you want to sync. You'll also need push — or read/write — access.
We use webhooks to improve workflow performance. To create those webhooks, the GitLab account you use with Unito must have Maintainer or Owner-level permissions. That's because we need the Configure project hooks permission. You can learn more about GitLab's user permissions here.
Bitbucket
Just like GitLab and GitHub, your account needs to be part of the organization that owns the repositories you need to sync and you'll need push access. Beyond that, you'll also need the issue tracker enabled on the repository, which is disabled by default.
Basecamp
Being a member of the Basecamp workspace that needs syncing should be enough. No special permissions required!
monday
No special permissions required!
OAuth Scopes
me:read | Read your basic personal details |
boards:read | Read boards data |
boards:write | Modify boards data |
users:read | Access data about your account's users |
updates:read | Read updates data |
updates:write | Modify updates data |
teams:read | Read teams data |
account:read | Access information about your account |
ClickUp
Just connect your account and you're ready to go.
Smartsheet
Add your Smartsheet account to Unito and you'll be ready to sync your Sheets. No additional permissions needed.
OAuth Scopes
CREATE_SHEETS | Create new sheets. |
ADMIN_WEBHOOKS | Create, delete, and update webhooks; get all webhooks; reset shared secret. |
READ_CONTACTS | Retrieve contacts. |
READ_SHEETS | Read all sheet data, including attachments, discussions, and cell data. |
READ_USERS | Retrieve users and groups for your Smartsheet organization account. |
WRITE_SHEETS | Insert and modify sheet data, including attachments, discussions, and cell data. |
DELETE_SHEETS | Delete sheets. |
What’s next?
Learn how to set up your first flow.
Learn how to map fields.
Not a Unito user? Try Unito for two weeks free!
Already a user? Sign in here!