Claim and evidence
It can also result in duplicate license costs if the IT team has purchased and provisioned a cloud product for the companyAtlassian · atlassian.com · 2021-07-19
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2026-11 The feature is still documented in Atlassian's current admin docs under shadow IT apps.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Bottom-up adoption leaves many small, separately paid or free instances inside one company. Showing them to IT turns scattered usage into a consolidation project that moves users and spend onto one central contract, and the discovery feature itself can sit in a paid admin or security tier.
How to run it
- Detect instances created by users on a company's verified domain
- List them for org admins with owner, user count and creation date
- Offer actions: join as admin, ask the owner to merge data, or remove
- Add a policy to allow new instances or require admin review
- Pair the view with a consolidated contract offer
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option ADiscovery in the security tier
Put automatic discovery of employee-created instances in a paid admin tier, as Atlassian does with Guard Standard.
- Option BMerge before removing
Let owners consolidate their data into an administered instance before the discovered one is deleted.
- Option CNew-instance policy
Let admins choose whether employees may create new instances freely or only after review.
Timeline
- 12021 Atlassian — Atlassian launched automatic product discovery so organization admins can find Jira and Confluence instances users created outside IT and consolidate them; it requires Atlassian Guard Standard.
- 22026-11 status checked: Working
Dated examples
- 2021
Atlassian
Atlassian launched automatic product discovery so organization admins can find Jira and Confluence instances users created outside IT and consolidate them; it requires Atlassian Guard Standard.
“It can also result in duplicate license costs if the IT team has purchased and provisioned a cloud product for the company”
✓ quote checked word-for-word on the pageatlassian.com · 2021-07-19
Does it still work?
The feature is still documented in Atlassian's current admin docs under shadow IT apps. source
Risks
- Users who built their own instance may resent being taken over
- Merging data across instances is costly and can break workflows
- Gating discovery behind a paid tier can feel like charging for control
Sources
- support.atlassian.com
“You may want to let the employee consolidate their data with an app you already administer before deleting the discovered app”
✓ quote checked word-for-word on the page - support.atlassian.com
“Shadow IT app s is what we call it when managed account users add Atlassian app s on their own.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (pass2-expansion-ops)