Confluence Slides is GA. So why does your site only show Present?

[#1]

This morning, 26 August, I went looking for Confluence Slides on an Enterprise setup. I opened a page, found Present in the more actions menu, pressed Ctrl Alt R, and got a beautiful full-screen view... of the wrong feature.

So I did it properly. Atlassian's documentation lists exactly four ways to start Slides. I checked every one of them, on two instances: a sandbox on the Preview release track and a production org on the Bundled track. The result is the most useful thing I can report today, and it is a number: zero of four entry points exist on either instance as of 26 August.

If you have made the same walk since the launch announcement, you are not alone and nothing is broken. Here is what is going on, how to tell the two "Present" features apart, and what is worth preparing before Slides actually lands.

Present is not Slides 🔍

The Present option on your pages is Presenter mode, in Confluence since around 2022. It renders the published page full screen with the chrome stripped away: selective section focus, a cursor spotlight, a dark theme toggle, a QR code for the audience. Genuinely useful for talking through a page. But it is not AI, it is not a deck, and it creates nothing: it is a view of the page you already have, and it ends when you press Exit.

Confluence Slides, GA since 17 August, is a different animal: an AI-generated slide deck that lives as its own Confluence content item. Rovo generates it from your pages, live docs, whiteboards, databases, Jira spaces and Goals, and through the Teamwork Graph it can pull context from connected third-party tools like Slack, Google Drive and Excel. Editing is AI-first: you describe changes in conversational language, or drag slides around yourself.

And a small vocabulary warning for the future: finished decks have their own fullscreen Present button too. So even after Slides arrives, the same word will mean two different things on the same site. Brief your service desk accordingly.

The four entry points, and where they are not 🚪

Per the official documentation, Slides starts from exactly four places:

1. Create menu: a Slides item under the Create button or the sidebar plus button
2. Create with Rovo: a Slides output button next to Live Doc, Whiteboard and Database
3. Remix: on any page or live doc, in the floating actions bar at the bottom right
4. Ask Rovo: requesting slides in chat

Here is what an Enterprise admin actually sees today. On both my instances, the Create menu lists Create with Rovo, Live Doc, Page, Whiteboard, Database, Folder, Blog, Smart Link and Space, and no Slides. Create with Rovo offers Live Doc, Whiteboard and Database as outputs, and no Slides. No Remix-to-slides, no slides from chat, and slides.rovo.com redirects straight back to Confluence home.

Why: the release track gate. GA on 17 August applied to sites on continuous releases. Per Atlassian's launch thread, sites on Release Tracks get Slides with the Preview track in September and the Bundled track in October. For most Enterprise orgs, "generally available" currently means "available in a few weeks."

Which hands you a free monitoring trick: your Preview-track sandbox is your early-warning system. When the Slides entry points appear there in September, you get roughly a month of rehearsal before Bundled production follows.

The second gate is Rovo itself. Slides is generated and edited through Rovo, so it arrives wrapped in whatever AI posture your org has chosen. If your organization restricts AI features for compliance reasons, note that Atlassian documents an Atlassian-hosted LLMs option for orgs that cannot send data to third-party model providers.

What the documentation already settles, and what it does not 🧭

Three questions your users will ask in week one, with honest answers as of today:

1. Who can see a deck? Settled, and cleanly: a deck added to Confluence goes under a parent item and inherits view and edit permissions from that parent. Your existing permission model governs decks. Two operational details worth knowing: the generation preview is private to its author until Add to Confluence, and closing the preview without adding it discards the work. Also documented: Rovo reads text from your sources and may reuse images based on placement, but does not ingest image content into the model.

2. Is a deck a snapshot or a live view of its sources? The documentation describes generation, not synchronization: Rovo reads your source material and builds the deck from it, and no refresh-from-source mechanism is documented. Until Atlassian states otherwise, the safe operating assumption is that a deck is frozen at creation, and updating it means asking Rovo to revise against the changed source. If your teams will present quarterly numbers from decks, that distinction matters in board meetings.

3. Where is the branding control? There is no admin surface for Slides themes or corporate templates today, nothing in Confluence administration. What the documentation does offer is prompt-level control, and it is explicit about it: give Rovo your brand colors as hex codes, and point at an existing deck as the template to match its layout, typography and spacing. That is convention, not governance. If brand consistency matters, the practical move is publishing a standard template deck and a standard prompt for your teams, and revisiting when (if) an admin surface ships.

What to prepare before it lands ✅

• Find your release track and calendar the month: Preview around September, Bundled around October. Watch the sandbox, it leads production.
• Settle the Rovo posture story now, including whether the Atlassian-hosted LLMs route applies to you, so the answer exists before the first "can we use this?" ticket.
• Brief your service desk on Present versus Slides. The confusion in this article's first paragraph will arrive as tickets, twice: once now, and again when decks add their own Present button.
• Review connector governance with generation in mind: what Rovo can read from connected sources, a deck can package and share.
• Draft the brand template deck and standard prompt now, so day one of Slides is not day one of brand chaos.
• Set the review norm for AI-generated decks that leave the team: Atlassian's own guidance says to verify AI results, and outward-facing decks are exactly where it matters.

The honest close

Slides looks genuinely promising: the doc-to-deck problem is real, and putting decks inside the permission model instead of a separate tool is the right architecture. But this launch is a lesson in reading the word GA carefully. For tracked Enterprise sites, the accurate sentence today is: the feature is coming in September or October, the Present button you can see is a different feature, and the preparation window is exactly now.

Two questions for the comments: which release track is your site on, and have any of the four entry points appeared for you yet? First-hand sightings with dates build the real rollout map faster than any announcement. 👇

Sources, verified 26 August 2026: Create AI-generated slides with Rovo, Create new content items with Rovo, Present your content with Presenter mode, Confluence Slides launch blog, Slides launch thread (release-track timing per Laura Eng, Atlassian Team).