Depending on your integration, Unito needs certain permissions. Here's our master list of what we need for each integration.
Which tools are covered in this article?
- Trello, Jira permissions
- GitHub, GitLab, Bitbucket permissions
- monday.com, Asana permissions
- Basecamp, ClickUp, Wrike permissions
- Zendesk, HubSpot permissions
- Slack, Smartsheet permissions
- Google Sheets, Notion permissions
- Intercom, Teamwork permissions
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.
What are OAuth Scopes? Open Authorization (OAuth) is a protocol that enables an application (Unito) to access specific data from another application (the tools you connect to Unito) without requiring your password. When setting up an integration, you'll need to grant certain OAuth scopes to Unito in order for your data to be synced effectively with other tools.
Regarding data security and privacy, rest assured Unito is SOC 2 Type 2 certified and all information is encrypted.
Trello permissions
The user account selected in your flow must be a member of the Trello Board you want to sync:
OAuth Scopes for Unito's Trello integration
Jira permissions
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.
Note that you need administrator permissions to connect your Jira account to Unito. Once the account is connected, you only need project-level admin permissions to create a flow.
If you get stuck on setting up permissions schemes in Jira, you can find a guide here.
OAuth Scopes for Unito's Jira integration
GitHub permissions
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 for Unito's GitHub integration
GitLab permissions
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 permissions
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.
Asana permissions
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 for Unito's Asana integration
monday.com permissions
No special permissions required!
OAuth Scopes for Unito's monday.com integration
ClickUp permissions
Just connect your account and you're ready to go.
Basecamp permissions
Being a member of the Basecamp workspace that needs syncing should be enough. No special permissions required!
Wrike permissions
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.
Zendesk permissions
Confirm that your Zendesk account has admin privileges. We need this in order to search for certain endpoints and create webhooks.
OAuth Scopes for Unito's Zendesk integration
|
'crm.objects.contacts.read',
'crm.objects.contacts.write',
'crm.schemas.contacts.read',
'crm.objects.deals.read',
'crm.objects.deals.write',
'crm.schemas.deals.read',
'crm.objects.companies.read',
'crm.objects.companies.write',
'crm.schemas.companies.read',
'crm.objects.owners.read',
'crm.objects.line_items.write',
'crm.objects.line_items.read',
'tickets',
|
HubSpot permissions
Only a HubSpot Super Admin can connect your account to Unito and create flows to sync tasks, tickets or deals.
OAuth scopes for Unito's HubSpot integration
| OAuth Scope | Definition |
|---|---|
|
crm.settings.properties.write |
Enables Unito to edit the settings of properties in your HubSpot CRM. This includes changing the name, description, group name, field type, options for dropdown fields, and other settings related to properties. |
| crm.objects.contacts.read | Allows Unito to read or retrieve contact information from your HubSpot CRM. |
| crm.objects.contacts.write | Enables Unito to create, update, or delete contact information in your HubSpot CRM. |
| crm.schemas.contacts.read | Gives Unito permission to read the structure or schema of your contact data in HubSpot. This includes information about what fields are available for contacts and their data types. |
| crm.objects.deals.read | Allows Unito to read or retrieve deal information from your HubSpot CRM. |
| crm.objects.deals.write | Enables Unito to create, update, or delete deal information in your HubSpot CRM. |
| crm.schemas.deals.read | Gives Unito permission to read the structure or schema of your deal data in HubSpot. This includes information about what fields are available for deals and their data types. |
| crm.objects.companies.read | Allows Unito to read or retrieve company information from your HubSpot CRM. |
| crm.objects.companies.write | Enables Unito to create, update, or delete company information in your HubSpot CRM. |
| crm.schemas.companies.read | Gives Unito permission to read the structure or schema of your company data in HubSpot. This includes information about what fields are available for companies and their data types. |
| crm.objects.owners.read | Allows Unito to read or retrieve owner information from your HubSpot CRM. |
| crm.objects.line_items.write | Enables Unito to create, update, or delete line item information in your HubSpot CRM. Line items typically represent individual products or services in a deal. |
| crm.objects.line_items.read | Allows Unito to read or retrieve line item information from your HubSpot CRM. |
| tickets | Gives Unito permission to read, write, and delete tickets in your HubSpot Service Hub. Tickets represent customer service issues or tasks. |
Smartsheet permissions
Add your Smartsheet account to Unito and you'll be ready to sync your Sheets. No additional permissions needed.
Required OAuth Scopes for Unito's Smartsheet integration
| SCOPE | This scope gives Unito permission to: |
| CREATE_SHEETS | Create new sheets in your Smartsheet account. |
| ADMIN_WEBHOOKS | Create, delete, and update webhooks, get information on all webhooks, and reset shared secrets. Webhooks are used to notify Unito when there are changes in your Smartsheet data. |
| READ_CONTACTS | Read or retrieve contact information from your Smartsheet account. |
| READ_SHEETS | Read all sheet data, including attachments, discussions, and cell data. This is necessary for Unito to sync this data. |
| READ_USERS | Retrieve user and group information from your Smartsheet organization account. |
| WRITE_SHEETS | Insert and modify sheet data, including attachments, discussions, and cell data. This is necessary for Unito to make updates to your Smartsheet data based on changes in other synced tools. |
| DELETE_SHEETS | Delete sheets in your Smartsheet account. |
Slack permissions
Add your Slack account to Unito and you'll be ready to sync your conversations. No additional permissions needed.
OAuth Scopes for Unito's Slack integration
Google Sheets permissions
During the authorization process, you'll need to give Unito access to your Google account so your flow can see and edit your sheets.
OAuth scopes for Unito's Google Sheets integration
Notion permissions
During the authorization process, you'll need to select the pages or databases you want to give Unito access to — along with its children.
OAuth scopes for Unito's Notion integration
Intercom permissions
To use Unito, make sure your Intercom account has "Can install, configure and delete apps" access turned on. You can find this under the Apps and integrations section of your user permissions.
Teamwork permissions
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.