How do I know if we have the Teamwork Collection?

[Barbara Szczesniak]

At my company, we already have the plan level of Confluence that we need (standard) and the different level of Jira that we want (premium). We use the features of Rovo that are available with these plans (currently, at least, with no cost). We have tried Loom and determined that we are not going to use it, so why would we pay for it?

Does this mean that we will never have the "Teamwork Collection?" Do you need to pay for the same level plan for all 4 applications to have the collection?

If we aren't going to have the collection, will the documentation content provided by Atlassian start to not apply to us? I already don't know whether I need to pay attention to everything I see about the Teamwork Graph.

We also have Jira Service Management, but don't need the other applications in the Service Collection. We have Bitbucket, but don't need/want the other apps in the Software Collection. If we were new customers, would we need to pay for all those other apps that we don't want?

[John Elder]

Barbara, awesome question!  As I understand it, it comes down to billing.  Purchasing a "collection" is just a bundle of apps that all go together within that collection and often include things that are widely purchased together.  You absolutely can still purchase individual apps and enjoy the full functionality of those apps, but a collection may be advantageous in pricing if you are on the bubble with something and not sure which way to lean.  For example, the Teamwork Collection (Premium) comes with Atlassian Guard... a lot of orgs add Guard as an add-on purchase to their Jira/Confluence purchases, so having Guard included along with Loom may make adoption of a tool like Loom easier and less expensive when done as a bundle.  I hope that makes ANY sense...?  :)

Here is a good link that explains it more: https://support.atlassian.com/subscriptions-and-billing/docs/how-billing-works-for-collections/

Teamwork Graph is different and refers to all the potential "connections" that the apps can obtain, both inside Atlassian and out.  The "Graph" might include Jira, Confluence, Outlook, OneDrive, Slack, etc.  Your Teamwork Graph can be built out without ALL of the Teamwork Collection apps.  

Please, someone, chime in if I have something wrong.  

[Amanda Barber]

I think you've nailed it, @John Elder!

Teamwork Graph info: https://www.atlassian.com/platform/teamwork-graph  

We use Teamwork Collection, but there are other collections now, too. They just bundle products for clear pricing. (Although I don't think Premium comes with Guard unless I'm missing something, haha!) 

I think the reason to move to a collection depends on team size and needs!