Suite or standalone

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Publishing is sold on its own and as part of the Capable Suite. The features are the same in both; several behaviours around them are not.

#What differs

THREE apps bundle the whole Publishing capability, not two: Publishing for Confluence (standalone), Capable for Confluence (the Suite), and Approval for Confluence. Customers of the Approval app get the full Publishing feature set even though the app is not named after it. Every statement about Publishing therefore has three variants.

Publishing for Confluence (listing 1238214); Capable for Confluence, the Suite (listing 1234376); Approval for Confluence (listing 1234761).

In the standalone Publishing app and the Approval app the "Capable Publishing" byline appears on every page the user can view (subject to the site-wide Hidden setting and the space's Never setting). In the Suite it additionally requires the space to have Publishing set to "Always", or the page to already carry a publish record. So in the

Standalone Publishing app: the space page, global page, space settings tab and global settings tab are all titled "Capable Publishing". Suite: they are all titled "Capable", with Publishing appearing as a section named "Publishing" inside the Capable space settings tab. Approval app: they are titled "Capable Approval", again with a "Publi

Works in the Suite and in the Approval app. It can never work in the standalone Publishing app, which does not include the Approval capability at all. So nothing there can ever queue an approval-triggered publish, and the "Publish approved pages" button is not shown.

The Suite subscribes to page-deleted and blog-post-deleted events; the standalone Publishing app and the Approval app subscribe to neither.

The publish record and all 13 of its search fields are named with a prefix unique to each app. "Publish status" in the Publishing app, the Approval app and the Suite are three completely different fields. A saved search or CQL query written for one app will not match another, and moving between apps loses all existing publish search data.

Supporting content types appear as "Capable Custom Content (Publish)" and "Capable Shared Storage (Publish)" in the standalone app and "(Suite)" in the Suite. These show up in Confluence content type lists and search.

The Publishing byline requires the viewer to be logged in, so anonymous readers never see it in any app. In the standalone Publishing app the space page and global page do allow unlicensed and anonymous viewers, but those viewers get a fixed "Powered by Capable" notice rather than any publishing data. Space and global settings are hidden

Publishing is a standard-edition capability. It is available on both Suite editions and is not behind any feature flag. Help lives at https://help.gocapable.com/confluence-publishing/.

#A few things worth knowing

  • Macro names usually differ: the standalone app tends to add the word macro.

  • Content is not shared between the standalone app and the suite, so moving across is a migration.

  • Anything described as working with another Capable feature needs that feature installed too.

Same features. Different neighbours.