LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • GitHub integration
  • Jira integration
  • Linear integration
  • Slack integration

Was this helpful?

  1. Resources
  2. Security & data retention

Data access

What data does Swarmia access and why?

GitHub integration

The GitHub integration is implemented as a Marketplace App. You can configure which repositories it has access to.

In the selected repositories, the app can access:

  • checks (read-only)

  • Github Actions (read-only) Added: Aug 16, 2023

  • Git contents (read-only)

  • GitHub Copilot Business (read-only) Added: May 14, 2025

  • deployments (read-only)

  • issues (read-only)

  • repository metadata (read-only)

  • repository administration (read-only) Added: Dec 9, 2022

    • Used to read the repository's branch protection rules

  • projects (read-only)

  • commit statuses (read-only)

  • pull requests (read-write)

    • Used to be able to comment on pull requests

At the organizational level, the app has read-only access to organization members, teams, and blocked users.

From each authenticated user, the app gets read-only access to their email address.

We subscribe to webhooks related to most of these same events.

We request the permission to access source code, as GitHub requires that for us to access your commits, but we never actually read your source code. For each commit, we only store the size of the change per file name. This allows us to estimate the complexity of the change, and also to ignore changes to automatically generated files (such as package-lock.json or Gemfile.lock).

At the user level, the Swarmia app requests permission to Act on your behalf. Swarmia uses this permission to reply to comments and post emoji reactions to GitHub as the user via our Slack bot.

Jira integration

The Jira integration is implemented as an Atlassian Connect application. The scope of the integration is:

  • Read (issues, comments, and projects)

  • Write (but not delete) – used for creating webhooks

  • Read user names and email addresses

Linear integration

For the Linear integration we request the following data access scope:

  • User emails addresses and names

  • Teams

  • Projects

  • Issues

  • Comments

Slack integration

The Slack integration is implemented as a Slack marketplace application. The scope we request is:

  • channels:join – join public channels

  • channels:read – view basic information about public channels

  • chat:write – send messages as @swarmia

  • groups:read – view basic information about private channels that @swarmia has been added to

  • incoming-webhook – post messages to specific channels on Slack

  • users:read – view people in a workspace

  • users:read.email – view email addresses of people in a workspace

On behalf of individual users who connect Slack notifications, we request an identity.basic permission.

PreviousSecurity & data retentionNextSwarmia IP Addresses

Last updated 15 days ago

Was this helpful?

GitHub permissions