Back to home

Integration permissions

Last updated September 30, 2026

Fulscrum connects to GitHub, Jira, and Slack. For each one, here is what it reads, what it never reads, what it can do, and the permissions it requests.

Minimum permissions

Fulscrum asks each integration only for the permissions it needs. You can start with GitHub and connect Jira and Slack when you are ready. See the privacy policy and the security overview for more.

GitHub

Connected as a GitHub App.

What Fulscrum reads

Pull request and review metadata: when a review was requested and from whom, review state, timestamps, and which repositories are connected.

What it never reads

Repository contents or source code. Fulscrum has no access to either.

What it can do

Read pull request and review information, and receive events when those change. A finding closes only when GitHub or Jira confirms the change.

Permissions requested

  • Pull requests: Read: read pull requests and their review requests and reviews.
  • Metadata: Read: read basic repository information, such as identifiers.
  • Webhooks: pull_request, pull_request_review: get notified when a pull request or one of its reviews changes.

Jira

Connected with Jira OAuth (3LO).

What Fulscrum reads

Only the projects and fields an administrator chooses: issue key, title and status, sprint membership, assignee, timestamps, issue links, and configured readiness fields such as estimate and acceptance criteria.

What it never reads

Issue descriptions or comments.

Readiness checks cover active-sprint issues only. Backlog issues are not monitored for them.

What it can do

Read the chosen Jira data. A finding closes only when GitHub or Jira confirms the change.

Permissions requested

  • read:jira-work: read issues, issue links, and status.
  • read:jira-user: read user and assignee information.
  • read:board-scope:jira-software: read boards.
  • read:sprint:jira-software: read sprints.
  • read:project:jira: read projects.
  • offline_access: stay connected without signing in again.

Slack

Connected as a Slack app that acts as a bot.

What Fulscrum reads

Replies in direct messages with the Fulscrum bot, and the email address used to match a person to their Slack account.

What it never reads

Your other Slack conversations or channel history.

What it can do

Send approved messages as the Fulscrum bot. Every outbound message requires explicit approval, and Fulscrum never impersonates a person.

Permissions requested

  • users:read.email: match a person to a Slack account by email.
  • chat:write: send approved messages as the Fulscrum bot.
  • im:history: read replies in direct messages with the Fulscrum bot only.
  • Event: message.im: get notified when someone replies in a direct message with the Fulscrum bot.

Questions? Contact us at hi@fulscrum.com.