Markdown settings

Global settings → Capabilities → Markdown: V

Site (Capable global setti

Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site (app property capable-global-hidden-capabilities). It does NOT stop existing macros from rendering.

Space settings → Space Capability Settings →

Space

Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property <APP_HASH>_capable under capabilities.alway

Global settings → Features → AI integrations

Site

'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. Studio additionally requires the app's

Global settings → Permissions

Site

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

Global settings → Egress domains

Site

Customer-approved domains are fetched and loaded directly by the reader's browser instead of going through the Capable proxy, which also makes their images loadable without a Capable token. Customer-managed egress is ena

Global settings → Indexing

Site

Runs on-demand backfill of the capable_refs content property that the byline count, the 'Used on Pages' panel and the markdown-ref CQL aliases all depend on.

Global settings → Migration

Site

Markdown is not on the tab's exclusion list, so the tab ships.

There is no Markdown-specific settings tab

n/a

It contributes only a byline, query actions, an asset browser, a Search panel, a custom content renderer, migrators and the two macros. Every switch above is a shared Capable settings surface.