Corma
Book a callBlog
  • Get started - Setup & implementation
  • Concepts and use cases
    • On & Off boarding
      • Define app owners
      • Create app bundles
      • Onboard a user
      • Offboard a user
      • Track provisioning progress
    • Expenses
      • CSV expense import
      • Inserting expense data manually
      • OCR Expense import
      • Contract Management & License Status Breakdown
    • Discovering Shadow IT
    • Access Requests
    • Employee view
    • Adding Applications to Corma
    • Licenses
    • App Analytics
  • The browser extensions
    • How to deploy Corma extensions with Google admin console
    • How to deploy Corma extensions with Microsoft intune
    • How to deploy extensions using GPO
    • How to manually install the Corma extension and login
    • How to deploy Corma extensions with Jamf
  • Integrations
    • Identity and Access Management
      • Google workspace
      • Microsoft Entra ID
      • Okta
    • Finance and accounting
      • Pennylane
      • Spendesk
      • Qonto
      • Candis
    • HRIS
      • Factorial
      • Personio
      • Lucca
      • Payfit
      • BambooHR
      • Deel
      • Hibob
      • Rippling
      • Workday
    • SaaS applications
      • Slack
      • Atlassian
      • Miro
      • Notion
      • LastPass
        • LastPass connection tutorial
        • LastPass Audit Log Collection
      • 1Password
      • Github Enterprise
      • Aircall
      • Hubspot
      • Salesforce
      • Intercom
      • Zendesk
      • Figma
      • Adobe
      • Canva
      • Asana
      • Front
  • General documentation
    • What is Corma?
    • General tech information
    • The Corma Glossary
    • Corma Product Roadmap
  • Security
  • Helpdesk
  • Changelog
Powered by GitBook
On this page
  • 1. On your Corma app go to the integrations page
  • 2. Under "Direct SaaS integrations" click on "Connect" for Atlassian
  • 3. Enter your Atlassian domain
  • 4. Enter the email associated to your Atlassian admin account
  • 5. Generate your Atlassian API token and insert it in Corma
  • 6. Generate your Atlassian API key
  • 7. Choose if you'd like Corma to synch all requests from Corma to a specific Jira project
  • 8. You've successfully connected Atlassian to Corma!
  1. Integrations
  2. SaaS applications

Atlassian

PreviousSlackNextMiro

Last updated 23 days ago

An admin Atlassian access is required to connect Atlassian to Corma

1. On your Corma app go to the integrations page

2. Under "Direct SaaS integrations" click on "Connect" for Atlassian

3. Enter your Atlassian domain

Your Atlassian domain is the link used to access your Atlassian workspace

4. Enter the email associated to your Atlassian admin account

5. Generate your Atlassian API token and insert it in Corma

To generate your Atlassian API token you need to follow these steps :

Your Atlassian API token should begin with ATATT3x

6. Generate your Atlassian API key

To generate your Atlassian API key you need to follow these steps :

Your Atlassian API token should begin with ATCTT3x

7. Choose if you'd like Corma to synch all requests from Corma to a specific Jira project

In your JIRA settings make sure that the create issue screen displays the "assignee" as a field otherwise Corma will not be able to make a successful request to JIRA.

8. You've successfully connected Atlassian to Corma!

Data should be synchronized within the next 24 hours and will be synched every day to your Corma app.

1. Log in to 2. Click Create API token 3. Enter a label for the API token and click Create 4. Anyone can create the API token, but it is going to inherit the role/group permissions of that user 5. Navigate to Profile and visibility on the top nav bar 6. Ensure all users have their email marked as visible by "Anyone" 7. Copy and add your API token below

1. Log in to 2. Go to Settings > API Keys 3. Click Create API Key 4. Enter a label for the API token 5. Pick the option of creating an API Key without scopes 6. Click Create 7. Copy and paste the API Key below

To ensure users appear on the in Atlassian, your company domain must be verified. will guide you through validating your company domain, enabling Corma to correctly collect Atlassian data. This must be configured with extreme care to prevent the auto provisioning by Atlassian of paid licenses to unwanted users. Corma is not responsible for any misconfiguration on Atlassian's side of your "managed accounts" portal.

https://id.atlassian.com/manage/api-tokens
https://admin.atlassian.com/
Managed Accounts page
This tutorial
www.app.corma.io/integrations