What is it and why are we doing it?
Atlassian is introducing the ability for Marketplace Partners to use a standard, customizable end-user agreement to help streamline and simplify the process of negotiating terms with customers during the procurement process.
Today, customers often face significant delays and complexity because they must review and negotiate separate legal agreements with each Marketplace Partner, sometimes leading to months of back-and-forth. By providing an industry-standard template for end-user agreements, we aim to reduce friction for both customers and partners. Customers benefit by saving valuable time and effort during procurement, while partners—particularly smaller or newer ones—find it easier to attract enterprise clients without the daunting task of drafting legal terms from the ground up. Ultimately, this is designed to make app adoption and migration smoother for everyone, supporting growth and success across the Atlassian ecosystem.
What do Marketplace partners need to do?
To adopt the standard end-user agreement, partners should follow the instructions below:
- Add a new app version or edit an existing one.
- In the app version screen, click the “Links” tab
- Observe the new question “Use a standard agreement as your End User License Agreement for this version? ”
- If you select “Yes ,” a “Provider Specific Terms ” text box will appear. This box allows you to customize the base agreement as needed (for example, to specify a different governing law and jurisdiction) and attach any additional documents (such as links to Data Processing Agreements (DPAs)).
- If you select “No” , you will be able to enter a link to your own End User License Agreement.
Once the standard end user agreement is adopted, it will replace the link to your current End User License Agreement (EULA) on your app listing page. Customers will also be provided with a new link to access your Provider-Specific Terms.
The app installation screen will display both the link to the standard end user agreement and the Provider-Specific Terms.
Note: Provider-Specific Terms allow partners to customize the base agreement as necessary (for instance, to specify a different governing law and jurisdiction) and add any additional attachments (such as links to Data Processing Agreements (DPAs).
Updating your latest app version to use the standard end-user agreement
Changes to app listing
Changes to the installation flow
How does this impact Marketplace Partners?
Adopting the standard end-user agreement offers the following benefits:
- Standardization: Adopting the standard end-user agreement reduces the need for custom agreements and provides partners and customers with a best-practice standard baseline to start from.
- Efficiency: Adopting this standard end-user agreement focuses negotiations on a limited set of custom terms.
- Flexibility: While the standard end-user agreement provides a solid baseline, it is customizable, allowing you to make necessary adjustments to meet your specific business needs.
Who designed this standard end-user agreement?
The standard end-user agreement was created by Bonterms.
The Bonterms Standard Agreement was designed by a committee of 100 lawyers to offer a best-practice standard agreement that balances the interests of both Marketplace Partners and customers. This agreement is free to use and licensed under the open-source document license CC BY ND.
You can review the Bonterms standard end-user agreement here: https://www.atlassian.com/licensing/marketplace/end-user-agreement-v1. This is the agreement that partners and customers will enter into when adopting the Standard Agreement.
We welcome your feedback
This is v1 of our integration of Bonterms into the Marketplace, and we would very much welcome your feedback on the feature and suggestions for improving it. Please share any feedback in the comments section below.
FAQs
| Question | Answer |
|---|---|
| If Bonterms releases a new version of their standard end-user agreement, will my apps automatically be updated to this new version? | No, we will not automatically upgrade you to any new versions of the standard agreement. We understand that you would need to review any new version of the standard agreement with your legal team to ensure it still meets your business needs, and you may also need to update your Provider-Specific terms. Version control for the standard agreement may potentially be introduced in the Partner Portal in the future, which would allow partners to choose when to adopt new versions. |
| Why is the option to adopt the standard end-user agreement done at the App Version level and not the app or partner level? | Previously, partners specified their EULA link at the app version level, so we didn’t want to change this behavior when adopting the standard end-user agreement. We invite your feedback on the possibility of adopting a standard end-user agreement at a higher level, with the option to cascade these changes downwards. This could mean either adopting the agreement at the app level, allowing all app versions to inherit it, or implementing it at the partner level, ensuring that all apps and versions benefit from the standard end-user agreement. |
| Do I need to add the Provider-Specific terms every time I add a new version of my app? | When you introduce a new app version, your Provider-Specific terms will automatically be copied from the previous version. These terms are retained at the app version level, allowing you to update them in the new version while ensuring that the Provider-Specific terms from earlier versions remain unchanged. |