Reading service management pages
You read pages that contain these macros, and did not configure any of them.
Each covers the whole journey for that reader, from the first time they meet the app to maintaining what they built with it. None of them assumes you have met Forge, or care.
You read pages that contain these macros, and did not configure any of them.
You own a process or an ITIL 4 practice and have to show who does what.
You chair the monthly or quarterly review, and write it up afterwards.
You agree service levels, and then have to defend them.
You decide what gets installed, and answer for it afterwards.
Each guide is the whole journey for one role, screenshots included, and none of them assumes you have met Forge or care. If you are evaluating rather than using, the Confluence administrator’s guide is the one your security review will want.
The developer and maintainer guide is not published here. It documents continuous integration, deployment and the screenshot harness — the vendor’s own operations rather than anything a customer needs.
The screenshots in these guides are rendered from the app’s own source code in a local harness, using the same Atlassian design-system components Confluence uses to draw the macros. The page and dialog frame around each macro is deliberately plain rather than a copy of Confluence, so a live site will differ in the surrounding chrome and may differ in small details of spacing. The text, fields, messages and layout inside each macro are the app’s own. The people, services and figures in them are fictional.
One install by a site administrator, then nothing: no app permission to manage, no accounts to create, no licence to renew, and no change in cost at any number of users.
Not listed yet: it goes to the Atlassian Marketplace as a free app once it has passed review. The button opens your own mail client. You hear once, on the day it lists, and never again. What is in 2.7.0