App approval guidelines

After creating and testing your app, your next step is to submit it for approval. To uphold standards of quality and reliability that our customers expect, all publicly listed apps are subject to an approval process.

Please be aware we have introduced new security checks for new apps and new app versions to uplift the security baseline for all Marketplace apps.

Pre-requisites, if not complete, could delay the app review process. Verify the following and be ready to share them:

• Privacy and security tab and ticket approval
• Partner verification ticket
• Any pending security vulnerability ticket if there are vulnerabilities detected

Which apps need to be approved?

All new publicly listed apps need to be approved by Atlassian. Once an app is approved, routine version updates don’t require re-approval, except in the following cases:

• Payment model changes: For example, if your app changes from free or paid-via-vendor to a paid-via-Atlassian app.
• New app type: For example, if you offer new app types off your base app such as an App Edition, Atlassian Government Cloud, Isolated Cloud, or Multi App Compatibility

How long does approval take?

Approvals take 10-15 business days, but approval times vary depending on current volume and the Marketplace team’s availability. The team works through submissions in chronological order, and when reviewing your app, they will check the requirements and guidelines specific to your development platform and product.

Errors in your app submission can cause delays to your launch. To avoid resubmissions, follow the guidelines on this page.

It's common to experience a few rounds of the approval process, but if you believe your approval is taking too long, submit a question to our team.

Platinum, Gold, and Silver status partners receive expedited SLAs.

Approval criteria for all apps

All apps, free or paid, need to meet the following criteria:

• Doesn't break the host Atlassian app UI: The UI of the host Atlassian app should be functional and intact when your app is installed. If the UI breaks, your app will be rejected.

• Doesn't degrade host Atlassian app performance: Your app shouldn't significantly impact the host Atlassian app performance.

• Doesn't infringe Atlassian trademarks: Trademark infringement is an automatic rejection, so be sure to read our brand guidelines for Marketplace Partners before submitting your app. This includes visual assets as well as naming conventions. For example, Jira App X would be rejected, but App X for Jira would be approved.

• Performs as described: Your app does what it advertises.

• Provide marketing assets: Provide marketing assets like a logo, banner, and screenshots as defined by Building your presence on Marketplace. Declare these assets in the app descriptor. This is recommended but not required for free apps.

• Reasonable pricing: Your paid app should be reasonably and competitively priced.

• Provide documentation: Your listing should reference documentation that describes how to set up and use your app.

• Available source code for open-source apps: If your app is open source, ensure your source is publicly available. We recommend a hosting site like Bitbucket. Include a license file in your source code that matches what you report in the Marketplace.

• No advertisements: Your listing shouldn't contain advertising for other apps, products, or services. You can mention paid versions of the same app or products that complement your app. In the host product, your app should abide by the same rules. Reminders for upgrades, complementary products, or additional features are acceptable. We recommend placing these reminders in configuration screens.

• Free and paid external service elements are clear: If your app listing is free, ensure your app provides some useful function in the Atlassian app 'as is'. If your app requires a separate third-party account this must be clear. If a separate third-party account is required and is subject to payments and licensing, ensure this is clear. We recommend in most cases these apps be listed as paid-via-vendor, unless your app provides some useful functionality without the third-party account.

• Valid company email address for paid-via-Atlassian apps: Personal or generic domains (like Gmail or Yahoo) are not permitted for paid-via-Atlassian apps. The email must clearly match the submitting organization and be active for business use.

• No duplicate, separate listing(s): If your cloud app has the same essential functionality as an existing server app you've published previously, it should share the same listing. You can do this by clicking Create version from the App versions screen.

• Accept the Marketplace Partner Agreement: Upon submission, accept the Marketplace Partner Agreement.

• Ensure you understand your legal obligations.

• Fulfill the security requirements outlined in the security workflow

• Create a privacy policy

• Secure authentication: Whilst your app may make use of Basic authentication with Atlassian's product REST APIs for ease of development/speed during development, this shall not be the case for any public, approved app. Additionally, shared secrets from customer-installed apps shall be stored in a secure manner.

• Register with our Developer Community: At least one contact from your partner profile is registered with the Atlassian Developer Community for future correspondence.

Additional Considerations

• If an app requires any integration with a 3P app please provide integration testing credentials on the ticket.
• The submitter on the marketplace will by default have access to the ticket, if they dont, or someone else needs access, then they will need to create a support ticket from here.