What is the process of evaluation and adoption of Confluence Apps from the Marketplace?

[Ala Stolpnik]

Hello Confluence Cloud Admins, I'm building a Confluence App for the Atlassian Marketplace and I'm curious how in the different organization evaluation and adoption of a new Confluence App looks like.

Let's say a Product Manager thinks that a given app will be helpful for them and the rest of the organization. They don't have Atlassian admin permissions. What would be the process for them to test and evaluate the app and then eventually get it approved to install and potentially even pay for?

[Rune Rasmussen · Accepted solution]

The first thing we do is look into if the app functionality can be achieved using the built in features.
If it can't we need a good business case. The cost/benefit needs to make sense.

Then we reach out to other internal teams who will look into many different things. Some general and some specific to the individual app.

• Security and the permissions required by the app
• What kind of data is being processed and potentially sent outside our site
  • Where is that data being processed
  • Who has access to that data and where may the be located
• Can it be turned on/off on a pr. Space basis?

In general we need to make sure we're compliant with the GDPR and the our own internal values and requirements.

[Rik Fisk · Accepted solution]

we have a form to go through asking basic questions like

• What are the current apps being used for this purpose......maybe this is not replacing existing apps
• How many people actually need to use this tool -compared to the licensed number of users
• what are the license costs
• what advantage to our company would there be using this tool is there a cost saving moving to a Atlassian based tool or an efficiency reason

Then we assess it ,cost is a big issue for us ,so the business case needs to be good.

Only after this would be let them do a months trial.

[Nikki Hailey · Accepted solution]

The requestor reaches out to us through our support channel to request the trial. We require sign off from our team + the security team before we install it. We then assign a person from our team to trial it alongside the requestor to evaluate possible uses by other teams. If we then determine that the price is worth the benefits received through the trial, we will purchase it.

[Susan Waldrip · Accepted solution]

Hi @Ala Stolpnik , our team does a lot of what @Rik Fisk , @Rune Rasmussen , and @Nikki Hailey mentioned:

1. Do we even need it or can we use something we already have?

2. If we seem to need it, does it really do what we need?

3. What's the cost for the number of folks who will actually use it (e.g., admins vs. all our agents or customers)? Sometimes cost knocks it out even if we need it.

4. Get a trial and test it out.

5. If 1-4 are good, make a business case to management that it's worth the cost, extra time to back up, etc.

Good luck!