What it does
PlantUML Diagrams & Charts for Confluence embeds a full PlantUML editor directly in Confluence. You write plain-text syntax, hit render, and get a clean SVG or PNG diagram — no external tools, no copy-pasting screenshots, no hunting for the right template.
Key capabilities:
- Built-in PlantUML editor — write and render without leaving the Confluence page
- SVG & PNG output — sharp, scalable renders that look great in print and on screen
- Easy in-place editing — update the source text and re-render; changes propagate instantly
- Respects Confluence permissions — integrates with existing page permissions and comments model
- No external tools needed — stay within Confluence for maximum efficiency
Supported diagram types
Who is this for?
Six teams that adopt this immediately — each with a different diagram type and a clear workflow benefit.
SE Software engineer Backend / full-stack Sequence diagrams Documents API contracts and inter-service flows alongside the Confluence spec page. The diagram lives in the same PR review cycle as the code — no stale screenshots. Example: Client -> API : POST /order API -> DB : insert record DB --> API : order_id API --> Client : 201 Created | | SA Solutions architect Enterprise / cloud Component diagrams Maintains living Architecture Decision Records (ADRs) and system overviews. PlantUML source is version-controlled text — editable by any team member, no license required. Example: package "Data layer" { [Postgres] - [Redis cache] } [API gateway] --> [Postgres] |
|---|
| | |
|---|
PM Product manager B2B SaaS Activity / flowcharts Maps user journeys and feature flows in PRDs without switching tools. Stakeholders can review the diagram directly in Confluence comments — no Figma access needed. Example: start :User lands on pricing page; if (logged in?) then (yes) :Show upgrade CTA; else (no) :Redirect to signup; endif | | QA engineer Test automation State diagrams Visualises object lifecycle and edge-case transitions in test plan pages. State diagrams make it immediately obvious which transitions are covered and which are gaps. Example: [*] --> Draft Draft --> Submitted : submit() Submitted --> Approved : approve() Submitted --> Rejected : reject() |
| | |
|---|
TW Technical writer Developer docs Use case diagrams Embeds actor-level use case diagrams in onboarding guides and SDK docs. Non-engineers can read the diagram immediately; writers update it by editing a few lines of text. Example: actor Developer actor "End user" Developer --> (Authenticate via OAuth) "End user" --> (View dashboard) | | DM Data / ML engineer Platform team Class diagrams Documents entity relationships and feature store schemas alongside data pipeline specs. Class diagrams replace ad-hoc ERD screenshots that go stale the moment the schema changes. Example: class Event { +String event_id +DateTime timestamp +String user_id } Event "1" --> "*" Feature |
A quick example
Here’s a simple sequence diagram showing a login flow — this is all you need to write in the editor:
Getting started
- Install from the Atlassian Marketplace — search “PlantUML Diagrams & Charts for Confluence” or use the direct link below.
- Insert the macro on any Confluence page — use the “/” insert menu and search for PlantUML. The editor opens inline.
- Write your diagram syntax and preview — type or paste your PlantUML code, hit preview to render, adjust and save when happy.
- Publish the page — the diagram renders for anyone who views the page. No plugin install required for readers.
Full documentation is available on the RVS documentation space. There is also a Rovo integration available if your team is exploring AI-assisted diagram generation.
