Permissions
This page explains who can install GitConnect for Jira, manage integrations, and view development activity on Jira issues.
Installing the App
| Action | Required Access |
|---|---|
| Install GitConnect for Jira from the Marketplace | Jira site administrator |
Managing Integrations
Access to the admin console's Manage Integrations area - adding or removing integrations, connecting repositories, and managing credentials - is controlled by a dedicated Jira global permission: Manage Integrations - GitConnect for Jira with GitHub & GitLab.
- A Jira site administrator can grant this permission to specific users or groups from Jira Settings → System → Global permissions
- Granting this permission lets someone manage integrations without making them a full Jira site administrator
Viewing Development Activity
| Action | Required Access |
|---|---|
| View the Issue Activity panel, Git Commits tab, and Git Roll Up tab on an issue | Standard Jira issue view permission for the project, plus the View Development Tools Jira permission |
| View the project-level Git Commits page | Standard Jira project browse permission |
| Create a branch or pull/merge request from Jira | Issue view permission, plus write-level access on the underlying repository via the connected credentials |
Note: The View Development Tools permission is a standard Jira permission (configured in Jira's permission schemes, not by GitConnect for Jira itself) that must be granted to the relevant users, groups, or project roles before they can see any development activity on an issue.
Project-Level Repository Access
Each integration can be associated with all Jira projects (the default) or restricted to specific ones during setup - see Managing Connected Repositories. Restricting an integration to specific projects:
- Limits which projects can create branches or pull/merge requests in that integration's repositories
- Limits which projects' issues can be linked to that integration's Git activity
- Restricts access to the Repository Browser for that integration's repositories to the associated projects
Repository-Side Access
Access to the underlying GitHub or GitLab repository is controlled entirely by GitHub or GitLab, not by GitConnect for Jira. An OAuth grant or personal access token only gives GitConnect for Jira the same level of access the connecting account has on the repository - connecting a repository does not widen access for other users.
Tip: Use a service account's OAuth grant or token for organization-wide integrations, rather than an individual's personal credentials, so the connection does not break if that person leaves the team or has their access changed.