Skip to main content

Jira: Connect with a dedicated admin user

How to connect Journeys to Jira with a dedicated admin user

R
Written by Raul Castro Fernandez

By connecting the Jira app with a dedicated admin user, Journeys works in Jira through an account that belongs to your company, not to one person. The connection keeps working when someone leaves your team 🚀

🧠 Note: Use this setup if you need to invite or delete Jira users from Journeys. Otherwise you can connect with an Atlassian service account, which doesn't count toward your Jira user limit. See Jira: Connect with a service account

Before you start

  • You need to be an organization admin in Atlassian.

  • You need a shared email address for the new user, e.g. hr@company.com. A shared inbox means password resets and security emails reach your team, not one person.

  • The dedicated user counts toward your Jira user limit like anyone else.

Step 1: Invite the dedicated user

  1. Log in to Jira with your own admin account.

  2. Click the gear next to your profile icon, then User management.

  3. Click Invite users in the top right.

  4. Enter the shared email address and tick Give organization admin access.

    Journeys needs organization admin access to invite and delete Jira users.

  5. Click Next, then Grant access. You can leave the roles as they are.

  6. Open the invite email in the shared inbox and set up the user.

  7. Log out, then log in as the dedicated user.

Step 2: Add the user to your Jira projects

Journeys can only work in projects the dedicated user has been added to.

  1. Open the project in Jira, click the three dots and select Space settings.

  2. Click Add people and search for the dedicated user's name.

  3. Set the role to Administrator and click Add.

  4. Repeat for every project you want to use with Journeys.

Step 3: Create an API token in Atlassian

  1. Make sure you’re logged in as the dedicated admin user.

  2. Go to Atlassian's API tokens page and select Create API token. Don’t choose the option with scopes. A scoped token won’t work with this connection.

  3. Name it “50skills_Journeys”, pick an expiration date and select Create.

  4. Select Copy and save the token somewhere safe. You can’t get it back after this step. You’ll paste it in step 4.

🧠 Note: API tokens expire after one year at most. Set a reminder to create a new one before it expires, or your Jira actions will stop working.

Step 4: Connect in Journeys

  1. In Journeys, go to the app marketplace, find Jira, and select Connect.

  2. Choose the Basic auth option.

  3. Fill in:

    • Jira site: the part before .atlassian.net in your Jira address

    • Email: the dedicated user’s email

    • API token: the token from step 3

  4. Then click Connect.

If it succeeds, you're ready to use Jira actions in your journeys 🚀

Related Articles
Did this answer your question?