Setup: Integration Permissions

Here’s a quick reference of the permissions required to set up each integration. Check this before set up to make sure everything’s ready to go.

Please note, this is a general guide - your organisation may have custom permissions or settings for some tools which differ to the roles we have described below. We endeavour to keep this as accurate and up to date as possible.

Must have before onboarding: Version Control System

GitHub

Required role: Organization Owner Note: You must have admin access to select repositories and Github teams/contributors.

---

Issue Tracking

Jira

Required role: Jira System Administrator Note: Non-admin may request the app but this will require an additional approval step from your admin. View Jira integration instructions

Linear

Required role: Admin View Linear integration instructions

---

CI/CD Tooling

GitHub Actions

Required role: Any Organisation admin View GitHub Actions integration instructions

Deployments API

Anyone with edit permissions in your CI/CD tool can set up the POST request to our endpoint using the token generated in Multitudes View API setup instructions

Note: We currently only allow either Deployments API or GitHub Actions to be configured.

---

Incident management

PagerDuty

Required role: PagerDuty Global Admin or Account Owner View PagerDuty integration instructions

OpsGenie

Required role: Account owner or Global Admin Note: This is the typical permissions level required to generate an API key in OpsGenie View OpsGenie integration instructions

---

Meetings

Google Calendar

Required role: Google Workspace Administrator View Google Calendar integration instructions

Outlook Calendar

Required role: Privileged Role Administrator View Outlook Calendar integration instructions

---

AI tooling

Claude Code

For the API (Claude Console) plan: Required role: Admin role Note: You will need to provision an Admin API key (different from a standard API key). View Claude Code integration instructions

For Teams and Individual plans: Required role: Any View Open Telemetry integration instructions

For Enterprise plans: Required role: Primary Owner View Claude Code integration instructions

Codex

Required role: Any View Open Telemetry integration instructions

Cursor

Required role: Admin role Note: Must be on the Teams or Enterprise plan. View Cursor integration instructions

GitHub Copilot

Required role: Organization Owner Note: You must have admin access to select repositories and Github teams/contributors. View GitHub Copilot integration instructions

---

Notifications

Slack

Required role: May require Slack Workspace Owner Note: Different organisations have different permissions required to install apps to a Slack workspace. If your workspace requires "app approval" you will need a Slack Workspace Owner to install or approve the Multitudes integration. View Slack integration instructions

---

Have any questions about your setup or integrations? Contact us at [e-mail]