Kroki diagram gateway
Every fenced diagram language is rendered server-side into a static SVG by Kroki, not by mermaid.js in the browser. Rendering requires a Capable client token. The self-hosted (customer-run) renderer code path exists but is currently switched off by a hard kill switch, so every markdown diagram goes through the Capable gateway regardless of a tenant's saved Diagrams setting. Tikz fences reject LaTeX file-I/O commands (\input, \include, \lstinputlisting, \openin, \write and friends) with a security error.
#Where you do it
Task | Where |
|---|---|
Insert an image or diagram from the Capable library | Editor toolbar → + → Image 'From library' or Diagram 'From library' |
Draw a diagram inline | Editor toolbar → + → Diagram 'From code', then edit the fence |
Publish markdown to a static site | Capable Sites (Suite or the Sites app) |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Permissions | - | Controls edit access to the GLOBAL asset store. Which is what governs who may create Global markdown templates. It is shared with diagrams, images, calendar and search because they all use one Confluence custom content t |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
AI diagram repairs per generation | 3 | Only the first three fenced diagram blocks in a generated document are validated and repaired; anything beyond that, and any language outside the seven repairable ones, passes through verbatim. |
#Related
Better with company.
