Add a new Atlassian app or collection to your organization

There are a few ways to add an app or collection to your Atlassian organization:

  • For new customers: Start a free trial from www.atlassian.com

  • For existing customers: Start a free trial from Atlassian Administration

  • For enterprise customers: Reach out to your partner or a sales contact to get started on the right plan

While existing customers can add an app from www.atlassian.com, we recommend following the steps on this page to add apps from Atlassian Administration. This ensures you’re adding apps to an existing organization.

Add new apps to an Atlassian Government Cloud organization

Contact Carahsoft or your Atlassian sales contact to add a new app to your Atlassian Government organization. Learn about Atlassian Government Cloud

Add an app or collection

Who can do this?
Role: Organization admin

  1. Go to Atlassian Administration. Select your organization if you have more than one.

  2. Select Apps > Atlassian apps > Add app.

  3. Follow the prompts to set up your app or collection.

  4. Select Add/Start trial.

It may take a few minutes to build your apps. We’ll send you an email when they’re ready and you’ll see the apps as part of your organization.

We start you on a free trial of the app or collection, either on a Standard or Premium plan. At the end of the trial, you’ll start paying for the plan. If we don’t have your payment details, we will change your app to a Free plan. Understand how Atlassian apps are billed

Add more apps on an Enterprise plan

If you already have an existing Enterprise plan, read about how to add and remove more Enterprise apps.

If you want to add apps on a new Enterprise plan, read this guide to get started.

With an Enterprise plan, you can add up to 150 instances of an app for your organization.

Exceptions

There are some apps and collections you can’t add to your organization by yourself from Atlassian Administration such as Jira Align and Strategy Collection. You will need to contact us to add them for you.

Some other things you need to know:

If you see your Bitbucket workspace under Atlassian apps in Atlassian Administration, you can skip this section.

Linking your Bitbucket workspace enables unified administration, billing, and access management across Atlassian cloud products. You can also see activity from the workspace in your organization’s audit log.

The workspace will appear in your Atlassian apps page once it’s linked.

If you have a Bitbucket workspace that wasn’t created from Atlassian Administration, you may receive a notification prompting you to link your Bitbucket workspace to your Atlassian organization. If you've already completed the linking process, you can ignore the notification.

If the workspace is already linked to another organization, you won't be able to unlink it or link it to another organization. Also, personal Bitbucket accounts can’t be linked, only workspaces are eligible.

Who can do this?
Role: Bitbucket workspace admins who are also Organization admins.

To link a Bitbucket workspace to your organization:

  1. Go to Atlassian Administration. Select your organization if you have more than one.

  2. Select Apps > Atlassian apps.

  3. Select More actions (•••).

  4. Select Link Bitbucket.

  5. Follow the prompts to finish linking your workspace. You can link one workspace at a time.

Manage users and access for linked workspaces

Linking doesn’t change your current user access, group permissions, or admin roles in Bitbucket. All existing users, groups, and permissions remain the same after linking, and are managed in Bitbucket. You can manage this in Atlassian Administration by adding the workspace through Apps > Atlassian apps > Add app.

Understand billing for linked Bitbucket workspaces

Linking your Bitbucket workspace doesn’t immediately change your billing method or combine your bills with other Atlassian apps. You'll continue to be billed for Bitbucket as you were before linking.

Impact of linking for integrations and service accounts

Existing integrations, service accounts, and automation setups aren’t affected by linking your workspace. Your pipelines, build processes, and integrations will continue to work as before and no changes are made to API tokens or service account access.

How linking Bitbucket affects security

Security settings, such as multi-factor authentication and key/token access, remain unchanged after linking and you can continue to use your existing security configurations.

Troubleshoot issues when linking a Bitbucket workspace

If you encounter errors while linking your Bitbucket workspace to your Atlassian organization, use the following guidance to resolve common problems:

Workspace already exists

  1. Review your organization’s apps list in admin.atlassian.com and check if your workspace is already linked.

  2. If the workspace is already linked, no further action is needed.

  3. If you are creating a new workspace, choose a different, unique name.

No workspaces to show

Make sure you are logged in with the correct email address that has admin rights for the Bitbucket workspace.

  1. Confirm you are both a Bitbucket workspace admin and an Atlassian organization admin.

  2. If you have multiple Atlassian accounts, try logging in with the account associated with the workspace.

Bitbucket missing in the interface

Verify you have the required admin permissions for both the workspace and the organization.

  1. Try accessing the Atlassian administration using a different browser or incognito/private mode.

  2. If the option is still missing, contact Atlassian support for assistance.

If you encounter any other errors, contact Atlassian support with the error message, your account details, and the steps you’ve taken.

 

Still need help?

The Atlassian Community is here for you.