This section provides information on the authorization required for each service
and the scope of collaboration when linking services.
Table of Contents
Authority and scope of cooperation required for service coordination
Authorization on each service side | Scope of cooperation | Notes, precautions, etc. | |
Google Workspace |
User administrator privileges or higher in an administrator role (privileged administrator is also acceptable) ※ To log in as a user who does not hold an administrator role, click here. |
Google account issued for employees in addition to the email address used to create each service when linking various services. | |
Slack |
Accounts with Slack app installation privileges |
|
|
Jira |
Managers of the organization |
All projects that can be viewed by collaborators | |
Backlog |
Manager |
All projects in which the collaborator is participating | |
Asana |
Workspace Member |
All projects that can be viewed by collaborators |
|
GitHub |
Managers of the organization |
All repositories that can be viewed by collaborators |
|
Notion |
Similar to Slack integration |
All notions linked to the target Slack channel |
|
Figma | owner/admin | All Figma teams that can be viewed by collaborators |
|
Reference Articles
Please refer to the following page for reference articles on the authorization required for service linkage and the scope of linkage.
Google Workspace
- Our Help Page -
Jira
- atlassian.com -
https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/
- Our Help Page -
Slack/Notion
- Slack help center -
https://slack.com/intl/en-gb/help/articles/1500009181142-Manage-app-settings-and-permissions
- Our Help Page -
GitHub
- GitHub Docs -
- Our Help Page -
Figma
- Our Help Page -
Comments
0 comments
Article is closed for comments.