How Atlassian's Atlas migration left a gap (and how teams are filling it)

Here's a small, telling episode in the history of a very common problem.

Atlassian — the company whose tools this whole problem lives inside — once built a product specifically to solve it. It was called Atlas, and its job was to let teams post short project status updates that stakeholders could follow. Crucially, it was widely used to keep non-technical, often unlicensed people informed: the executives, clients, and sponsors who need to know how a project is going without living in Jira.

I want to dwell on that for a second, because it's the most important fact in this article: Atlassian built this feature. Which means Atlassian agreed the need was real. The gap you feel — that there's no clean way to keep non-Jira people in the loop — isn't your imagination. The vendor themselves once validated it enough to ship a product for it.

What changed, honestly

Over 2025, Atlassian began folding Atlas into its Platform Experiences, under the Atlassian Home umbrella. And here's where I have to be careful, because the honest state of what that did to unlicensed followers is genuinely murky.

In Atlassian's own community discussion about the change, the accounts don't agree. An Atlassian representative indicated that following projects and receiving the weekly update doesn't require a paid seat. Customers in the same thread reported the opposite in practice, and worried aloud that the migration had quietly turned their free stakeholders into billable ones. One put it memorably — that it felt as if Atlassian had "monetized" their project updates.

I'm not raising this to pile on Atlassian. Migrations are hard, platforms get consolidated, and I'm sure there were real reasons. I'm raising it because of what the confusion itself tells you.

The confusion is the whole problem in miniature

Think about what it means that, after the migration, even the people in the official thread — staff and customers together — can't cleanly settle whether an unlicensed stakeholder can still just follow a project and get updates.

It means the simplest possible version of this need — "let a non-technical person quietly stay informed, without buying them a seat" — is somehow still unresolved, still license-shaped, still confusing, inside the flagship product suite built for exactly this. If keeping a client in the loop feels like it should be trivial and somehow isn't, you're not missing an obvious setting. The obvious setting is genuinely contested.

That's the gap. Not that Atlassian is villainous, but that a real, validated need keeps not having a clean, cheap, obvious answer — and the one time there was a product aimed squarely at it, it got folded into something bigger and the clarity got lost in the move.

How teams are filling it now

So what do you actually do today? The honest menu, matched to who your stakeholder is — and worth noting up front, this is the same licensing terrain Jira itself never resolved either; see gwhat Jira guest access actually offers if the "unlicensed" question goes beyond Atlas specifically:

Jira Automation emails. Native, free, and underused. A scheduled automation rule can email a summary to any address, including people with no Atlassian account. It's push-only and capped by plan, and raw event emails need a human to make them readable — but as a way to get information out to unlicensed people, it's real and it's built in. (For the full walkthrough of setting one up, see our guide to gJira automation weekly summary emails.)

A sharing app, matched to the need. This is where most teams land, and the fork matters. If your stakeholder is a collaborator who needs the real board, External Share for Jira gives external users genuine access without licenses. If your stakeholder is a reader who just needs to know the project's okay, a status-page app is the better fit — that's the space I work in with gClientLens, which turns a project into a plain-language status page shared by link. Different tools for different stakeholders; picking the wrong one is the usual disappointment. (See our full comparison of gExternal Share vs. ClientLens for the detailed breakdown.)

Confluence, if the stakeholder already has access to it — a live page beats a stale PDF, though it quietly costs a seat if they don't.

None of these is Atlas. But collectively they're how teams are answering, in 2026, a question Atlassian itself once thought was worth building a whole product to answer — and, in the answering, quietly confirmed was worth building for in the first place. (For the complete menu of options — licenses, automation, apps, Confluence — see gour full guide to sharing Jira status without a license.)

---

I'm Andrey. I build small, focused apps for Jira at gGuenov Labs. I write about the surprisingly unsolved problem of keeping non-technical people informed about technical work.