.webp)
Avaratak Blog
Confluence Slides: The Deck That Never Leaves the Building
Somewhere in your company right now, a perfectly good Confluence page is being copied into PowerPoint one text box at a time. By Thursday there will be a deck. By Friday there will be four versions of the deck in an email thread, and nobody will be entirely sure which one the VP actually saw. The knowledge didn’t change — it just left the building, and the moment it left, it started to rot.
Atlassian would like that trip to stop happening. On August 17, 2026, the company announced Confluence Slides, an AI-generated presentation format that lives inside Confluence itself. You describe the deck you need, Rovo builds it from work your team has already done, and the result gets added to a Confluence space like any other content item. No export, no blank slide, no version fourteen.
What Atlassian actually shipped
Confluence Slides is a new content type, generated and edited with Rovo. From a single prompt, Rovo determines the slide structure, writes the content, and builds the visuals — charts, timelines, bar graphs, images — grounded in your existing material. According to Atlassian’s documentation, it can draw on Confluence pages, live docs, whiteboards, databases, Jira, Goals, and connected third-party sources such as Slack, Google Docs, and Microsoft Excel.
There are four ways in: pick Slides from the Create menu, use Create with Rovo, hit Remix on any page or live doc, or simply ask for a deck in Rovo Chat. Generation happens in a private preview area; only you can see the draft until you select Add to Confluence, and if you close the preview without adding it, the draft is gone. Once added, the deck sits in the content tree under a parent item, carries inline comments and version history, and supports collaboration with up to 60 other people. There is a built-in presentation mode, so the path from prompt to podium never leaves the product.
Editing is AI-first but not AI-only. You can ask Rovo for global changes (“shorten every slide to three bullets”), have it redesign a single slide, or click into any element and fix it by hand, the old-fashioned way.
The part worth slowing down for
The headline feature is AI generation, and the demo videos are suitably slick. The more consequential design decision is quieter: the deck is a Confluence content item. It inherits view and edit permissions from its parent. It shows up in the content tree. It has watchers, comments, and a version history.
Think about what a presentation normally is: an export. The moment knowledge becomes a .pptx attachment, it leaves your permission model, your search index, and your version control, and begins a social life of its own. Every deck is a fork of the truth, and forks drift. Slides is Atlassian’s bet that if the deck never leaves the system, the fork never happens — the presentation stays as current, governed, and findable as the page it came from.
That framing also explains why this is not just Atlassian chasing a crowded AI-presentation category. Plenty of tools can generate attractive slides from a prompt. Far fewer can generate them from your project brief, your Q3 retro, and your Jira data, then file the result next to the source material with the same access controls. As we argued when Atlassian’s Q4 letter put the Teamwork Graph at the center of its strategy, accumulated context is the asset you cannot hire — and Slides is another surface where the graph, not raw model horsepower, does the heavy lifting. It also extends the connector story we covered when Rovo learned to read Google Drive and SharePoint: every source you wire into the graph now feeds your decks too.
The fine print your admin will ask about
- Availability. Rovo is available to customers on Standard, Premium, and Enterprise Cloud plans of Jira, Confluence, Jira Service Management, or the Teamwork Collection, and Atlassian notes the rollout to some eligible plans is still completing over the coming months. If Slides has not appeared in your Create menu yet, that footnote is probably why.
- Data Center. There is no native equivalent. Atlassian’s guidance is that full Rovo AI requires a cloud plan, with Data Center connectors available to sync data into cloud environments. File this next to the other entries on the migration ledger.
- Image handling. Rovo reads the text of your source material and may infer which images are relevant from their placement and surrounding text. Atlassian states that Rovo does not ingest or scan your image content into the AI model — a detail worth having ready before the security review asks.
- The permission nuance. Generation is scoped by what the prompting user can access; once generated, the deck’s own inherited permissions govern who sees the content. That is exactly how copy-paste has always worked — Slides just makes the copy dramatically faster. If you use content classification in Confluence, generated decks deserve the same discipline as pages. This is the same lesson from the context gap between AI and your actual business: the more context you feed the machine, the more the output inherits your governance obligations.
Who should care, and what to do first
Teams with recurring readouts are the obvious pilot: campaign analyses, program kickoffs, roadmap reviews, customer pitches. Atlassian’s announcement cites Nielsen research putting slide work at roughly seven hours per week for corporate professionals, with 37 percent of PowerPoint time going to formatting and another 42 percent to hunting for templates and old slides. Treat vendor-cited numbers with the usual seasoning, but nobody who has nudged a text box at 11 p.m. thinks the direction is wrong.
Practical first moves: confirm Rovo is enabled on your plan; pick one team with a deck they rebuild every month; establish a prompt convention that includes your brand hex codes, a reference template, and the intended audience; and decide where decks live in the tree so they inherit sensible permissions from day one.
Then fold the new content type into your lifecycle habits. Slides join pages, live docs, whiteboards, and databases in the tree, and stale decks accumulate exactly like stale pages. The gardening discipline from our guide to keeping a Confluence estate alive applies here without modification. And keep human review where it matters: a board deck or a regulator-facing readout still deserves eyes on every number Rovo pulls.
The Avaratak Take
AI slide generators are a crowded category. The interesting move is not that Atlassian built one; it is where they put it. By making the presentation a governed, permissioned, versioned neighbor of the document that spawned it, Atlassian is attacking the deck’s real problem — not that it is slow to make, but that it becomes an ungoverned fork the moment it exists. It also completes a pattern we have been tracking all year: Rovo went from answering questions, to researching whole topics, to now producing the artifact you carry into the meeting.
What I would watch: whether generated decks hold brand discipline at scale (a hex code in a prompt is a suggestion, not a design system), whether present-from-Confluence survives contact with executive meeting rituals, and whether teams remember that a fast deck is not the same as a good argument. Rovo can structure a narrative in seconds; deciding what that narrative should claim is still your job, and it was never going to be automated.
If you are working out where Slides fits your Confluence estate — or whether your Rovo rollout is ready for it — Avaratak’s senior Atlassian consultants can help you separate the useful part from the shiny part. Book a discovery chat if a second opinion would help.