Rate this page:
As the Marketplace is migrating to a new billing and subscription management system, you would be experiencing a few changes in the UI. Please refer to the changes in the documentation for the updates. The documentation will be updated in segments as we update our billing system.
The Atlassian Marketplace facilitates the distribution and sale of apps built for Atlassian products. With the Marketplace, one can get hassle-free access to Atlassian’s large customer base and sell apps to people who are already using products like Jira and Confluence. There is no cost to list apps on the Marketplace, and along with that, there are multiple benefits that you can avail of:
Prefer a video tutorial? Follow along to learn about Atlassian Marketplace, the elements of an app listing, and Atlassian’s app approval criteria in this overview video. This video is part of our tutorial series, Cloud Cafe. It is a series to learn about cloud app development with Atlassian.
In the Marketplace, we welcome free apps, open-source apps, or apps sold directly by partners. This means you can offer free apps, or apps that use your own checkout and licensing system. However, using different payment models means you have access to varying perks of the Marketplace:
Listing an app in the Marketplace means you agree to the Marketplace Partner Agreement. This agreement is between Atlassian and you as a partner.
It also means you agree to comply with Atlassian's brand guidelines. These guidelines govern how you should represent your company and your apps in relation to Atlassian.
Apps belong to partners. A partner profile describes the company that "owns" the app. For example, Atlassian and Gliffy are partners. If you're an individual author without a parent company, (e.g., Ross Rowe) then create a partner profile using your name. Your user account must be associated with a partner profile before you can modify that partner's app listing.
To create your partner profile on Marketplace:
If your account should belong to a particular partner but doesn't, ask somebody on the account to add you. Here's how they can do this:
If there is no other user for your partner profile, then contact the Atlassian Marketplace and we'll add your information for you.
A Marketplace partner can add contacts to their account defining who can access specific parts of the app management. An admin from MP can access all the app management capability with others have access to specific capabilities like - creating promotions, managing price etc.
For Atlassian teams to reach out to Marketplace partners, say for processing refunds or looking for partnership to run campaigns or to reach out for security related issues or to conduct closed beta programs, there is no easy way to know who to reach out to and reaching out to all the contacts is not feasible.
Primary Contact - the go-to person/people/account to contact regarding any of the concerned areas
Support Contact - the senior support figure to be contacted in relation to existing support cases customers have with the partner if escalated to Atlassian
Licensing/Finance Contact - person/people/account who can be contacted for licensing/payment queries or etc
Security - person/people/account who can be reached quickly when security incidents are reported/point of contact for all security-based queries i.e. bug bounty program
Marketing - person/people/account our Marketing team can connect with for joint marketing endeavors
Engineering - person/people/account for informing of upcoming technical changes i.e. API alterations, functionality retirement etc
Migrations - the senior support figure to be contacted in relation to Cloud migration specific support cases
Sales support & approvals - person/people/account who approves sales-centric requests such as pricing questions or discount approvals
Note - Please update the roles whenever there is a change in ownership of a point person, this will help us reach out to the right contact.
The Universal Plugin Manager (UPM) can install apps automatically into Atlassian products. However, some items in the Atlassian Marketplace may not be suitable for automatic installation.
The Publish a new app form has a Deployable option that indicates whether an app installs with UPM. You should not check the Deployable option if your app consists of multiple JARs. The Atlassian Marketplace and UPM do not support Try, Buy, Install, Upgrade, and Renew buttons for non-deployable apps. Non-deployable apps cannot be sold under the Atlassian Marketplace Partner Agreement as they do not support the UPM licensing API.
Additionally, if your app requires multiple downloads, configuration or license files on the file system, or if your app is not meant to be installed into the host product (like Jira Client, for example), then do not check the Deployable option. Your app is still available for download, but the UPM does not attempt to install it in the host product.
To contact Atlassian directly about an app listing, make a request to the Atlassian Marketplace.
If you offer support for your app, the Get support button is on the Support tab on your app details page. This tab also lists other resources including documentation links, issue trackers, forums, and more. App customers are discouraged from writing reviews to get support, and should instead contact Marketplace partners directly.
Rate this page: