# Integrations

> Connect Orangescrum to the tools your team already uses — Git, Azure DevOps, Google Workspace and more.

> For the complete documentation index, see [llms.txt](https://helpdesk.orangescrum.com/llms.txt).

Source: https://helpdesk.orangescrum.com/guide/cloud/integrations/overview

---
> **Pro and Premium**
>
> Git sync and Google Workspace integrations require Pro Unlimited or above.
> SSO is Premium. See the
> [feature matrix](https://helpdesk.orangescrum.com/guide/cloud/plans/feature-matrix).

## What's available

- [Git sync](https://helpdesk.orangescrum.com/guide/cloud/integrations/git-sync): GitHub, GitLab and Bitbucket. Link commits, branches and pull requests to tasks.

- [Azure DevOps](https://helpdesk.orangescrum.com/guide/cloud/integrations/azure-devops): Sync work items between Orangescrum and Azure Boards.

- [Google Workspace](https://helpdesk.orangescrum.com/guide/cloud/integrations/google-workspace): Calendar sync and Drive attachments.

- [Developer API](https://helpdesk.orangescrum.com/guide/api/introduction): Build your own — 59 REST endpoints. 

- [MCP / AI Connect](https://helpdesk.orangescrum.com/guide/mcp/introduction): Connect Claude, Cursor or Copilot directly. 

- [SSO](https://helpdesk.orangescrum.com/guide/cloud/admin/security): Single sign-on with your identity provider. 

## Choosing what to connect

Every integration is a thing that can break, produce noise, or drift out of
sync. Connect the ones that remove real manual work.

**Start with where you lose time**

    If people copy ticket numbers into commit messages by hand, Git sync pays
    for itself immediately. If nobody does that, it will not.

**One at a time**

    Connect it, use it for a fortnight, then decide whether to add another.
    Turning on five at once means you cannot tell which one is causing the noise.

**Set it up per project**

    Most integrations are configured per project, so each links to the right
    repository or calendar.

**Check what it generates**

    An integration that posts a notification for every commit will be muted
    within a week — including the notifications that mattered.

## Two-way sync needs care

> **Two-way sync means two sources of truth**
>
> When the same item exists in two systems and both can edit it, they will
> eventually disagree. Decide which system owns which field **before** turning
> it on — for example, Orangescrum owns priority and assignee, the other tool
> owns status.

This applies most to [Azure DevOps](https://helpdesk.orangescrum.com/guide/cloud/integrations/azure-devops).
Git sync is largely one-way and much safer.

## Permissions

Integrations authenticate as a user or an app, and inherit those permissions.

**Use a service account where you can**

    An integration wired to a person's account breaks when that person leaves.

**Grant the narrowest scope that works**

    Read-only if the integration only reads.

**Review connections periodically**

    Disconnect what nobody uses. Every live connection is exposure.

## When something stops syncing

**Check the credential first**

    Expired tokens and revoked access are the most common cause by a wide
    margin, and they fail quietly.

**Then check the mapping**

    A status or field renamed on either side breaks the mapping. Renaming
    statuses is a frequent trigger.

**Then check permissions**

    Someone's access changed, or a repository moved.

**Then reconnect**

    Re-authorising fixes a surprising proportion of problems.

## Building your own 

If nothing off the shelf fits, the [Developer API](https://helpdesk.orangescrum.com/guide/api/introduction)
covers projects, tasks, timelogs, users, test cases, defects and checklists.

- [Developer API](https://helpdesk.orangescrum.com/guide/api/introduction): 59 endpoints, HMAC-signed, with an OpenAPI spec.