SoftTech AI Registry
Atlassian · Confluence

Create with Rovo

A Confluence Cloud creation workflow, reached from the Create menu, in which a user supplies a natural-language prompt plus optional files, links, a template, @mentions and selected data sources, and Rovo generates a draft in a full-screen preview area. Atlassian documents that the preview has not yet been added to a space and is visible only to the creating user until the user selects Add to Confluence. The user may edit the preview directly, use slash commands, use selection-level AI actions, or refine it through Rovo chat. Persistent Confluence content is created only when the user selects Add to Confluence, chooses a space and parent item, chooses an output form for written content (live doc, draft page or whiteboard) and selects Add. Supported outputs documented for this workflow are pages, live docs, whiteboards, databases and slides. Previews are retained and can be reopened from Rovo chat history; Atlassian states that for slides, closing the preview without adding to Confluence means changes are not saved.

Recorded characteristics

Function
Atlassian documents the following sequence. The user selects Create in the top navigation, then Create with Rovo, and adds a prompt. The user may optionally add files, links, a template or an @mention of a person, choose which data sources Rovo uses, select a content type, use suggested starting prompts, and change the answering mode, then select Submit. Rovo drafts the content in a full-screen preview area which may contain written content, whiteboard elements, or a proposed draft of a database. The user can edit the preview by changing text directly, using the / slash command to insert elements, selecting content and using AI actions (Ask Rovo on a specific section, further AI actions, Improve writing), or continuing the conversation in Rovo chat. To persist the result the user selects Add to Confluence, chooses any space and parent item, and for written content chooses to add it as a live doc, a draft page or a whiteboard, then selects Add. Atlassian states that live docs, whiteboards and databases allow real-time editing while pages must be published, and that the user can continue editing after adding, including switching between live doc and page or converting to a blog post. For slides Atlassian documents the same Create with Rovo entry point: write a prompt, add links and files, select the Slides button to output, edit and refine in preview, then Add to Confluence choosing space and parent; the presentation inherits user view and edit permissions from the parent item. Atlassian separately documents three other ways to start slides (the Create menu, Remix from a page or live doc, and Rovo Chat), which are not part of the Create with Rovo entry point.
Data access
Atlassian documents the following generation context for Create with Rovo: the natural-language prompt itself; files, links, a template and an @mention of a person added through the Add control; and data sources the user chooses for Rovo to use. For slides Atlassian documents generation from the user's pages, live docs, whiteboards, databases, Jira spaces, Goals and more, and states that Rovo reads text from source material and may infer the relevance of images in that source material based on image placement and surrounding text, while not ingesting or scanning image content into the AI model. Atlassian states generally that Rovo Search respects user permissions so users only see what they already have access to. No tenant-wide retrieval authority beyond documented, user-selected sources is established for this capability.
Actions
Generative only
External actions
Unknown
Human confirmation
Required
Permission basis
User permissions
Administrative control
Organization admins manage Rovo access from Atlassian Administration under Rovo, then Rovo access, and can block individual apps from Rovo features; blocking an app disables all current and upcoming AI features for that app, including Rovo Agents and Chat, while content previously generated by Rovo remains. Atlassian specifically names Create with Rovo among AI features common across Jira family apps that remain available as long as any Jira app on the site still has Rovo enabled. Atlassian also documents that turning on Rovo requires the organization admin to be on a verified business domain, that AI activation is required for Rovo features that use AI, and that organization and billing admins can track Rovo credit usage, set spending limits and disable extra usage. Space-level Add content permission governs where a user can place content.
Default state
Conditional
Availability
Documented for Confluence Cloud. Atlassian states Rovo is available for apps on Standard, Premium and Enterprise plans, that everyone in the organization will have access to Rovo features, that Confluence is a supported app, and that Rovo is not available in Atlassian Government organizations. Atlassian notes some features may not be available in sandbox environments. No language restrictions and no regional restrictions specific to Create with Rovo are established.
Licensing
Atlassian states on the Create with Rovo documentation page that Create with Rovo is a premium AI feature that consumes Rovo credits. Atlassian documents that Rovo credits are included in all paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscriptions, with per-user per-month allowances pooled at the organization level (Confluence: 25 Standard, 70 Premium, 150 Enterprise), that allowances reset monthly and do not roll over, that credits are consumed by billable events where each invocation of an Atlassian agent or AI feature is a billable event, and that extra usage billing for Rovo credits takes effect on 3 December 2026 with extra usage enabled by default and admin spending limits available. The exact number of credits consumed per Create with Rovo request or per output type is not established.
External model or provider
Not established. Atlassian does not identify a specific model or provider for Create with Rovo. General Atlassian AI administration documentation notes that certain AI providers such as OpenAI may process data in non-EU regions, but this is not attributed to Create with Rovo specifically.
Limitations and uncertainty
Action capability is recorded as generative_only because Atlassian documents that the contents of the preview panel have not yet been added to a space, that only the creating user can see the preview, and that the user must select Add to Confluence, choose a space and parent item and select Add before persistent Confluence content exists. No Atlassian-documented AI-performed persistent write to a Confluence space occurs before that human action. External action capability is recorded as unknown: no external write by this capability is documented, and Atlassian provides no affirmative statement excluding external actions; retrieval from supplied links, files or connected sources is not treated as an external action. Permission basis is recorded as user_permissions on the basis that Atlassian documents Rovo respecting the user's existing permissions, that adding a page or blog post requires the space Add content permission, and that a slide deck added through this workflow inherits user view and edit permissions from its parent item; no separate execution identity for Create with Rovo is documented. Default state is recorded as conditional because Rovo requires an eligible Standard, Premium or Enterprise plan, a verified business domain, AI activation, an app not blocked by the organization admin, and available Rovo credits, and is unavailable in Atlassian Government organizations. Boundaries deliberately excluded from this record: editing existing Confluence content with Rovo in the editor, Remix, Rovo Chat as a separate surface, and configurable Rovo agents and agent collaboration through comments and the editor, all of which Atlassian documents separately and which are covered by other registry records. Not established for this capability: whether Add to Confluence can produce a database as a persistent content item (Atlassian documents a proposed draft of a database in the preview area and names databases among the outputs Create with Rovo helps you get started with, but the documented Add choices for written content are live doc, draft page or whiteboard); the precise persistence model and editability of a whiteboard produced by this workflow beyond real-time editing; whether the preview itself is retained server-side beyond appearing as a reopenable preview card in Rovo chat history; whether any formal AI audit log exists, as opposed to Rovo chat history and ordinary Confluence version history after content is added; and who is recorded as creator or author of content added through this workflow. Atlassian documents that Confluence pages support drafts and version history while live docs do not have drafts and show changes instantly, so a page added through Add to Confluence is a draft page that a human must publish separately; no page publication authority is claimed for Rovo. Atlassian's advisory to always review AI-generated content for accuracy before making it publicly accessible is recorded as documented guidance, not as a control.

Evidence