Leafward support

Last updated 18 August 2026

Before writing: the self-check

Leafward ships a diagnostic. Open the app, go to Coverage, and press Run self-check.

It asks Confluence, from inside the app on your site, whether each endpoint Leafward depends on still answers — the app's own account, the space list, space access, space roles, the directory lookup, page reads, the authorisation check and the subtree read. A screenshot of that panel answers most questions before they are asked, because the answer to “it isn't working” is nearly always one line of it.

This exists because an endpoint's availability differs by caller: an API that answers a user's browser can refuse an app. Nothing outside your site can tell you what your site allows.

Things that are working as intended

Leafward's own account is named in every restriction it writes

Confluence refuses any write that would lock out the account making the change. No app can avoid this.

Leafward asks whether you administer the space, not whether you can restrict the page

That is stricter than Confluence's own rule and it will refuse some people who could legitimately restrict a page by hand. For a tool that changes who can see what, refusing too often is the safer direction.

A newly created page is briefly unrestricted

Automatic inheritance reacts to a platform event that arrives about a second and a half after the page appears. That window is real and cannot be closed from inside an app.

A space with no readable page is reported as such, never as empty

If a data security policy hides a space from apps, its pages answer “not found” while the space stays listed — from inside an app that is indistinguishable from a space that is genuinely empty. Leafward says which of its spaces it could not read through, and refuses to guess why.

Leafward never says who can edit a page

It says whether anything restricts editing. Knowing who would mean expanding group membership, which no Confluence app can do.

A large cascade pauses

Confluence meters apps in points against a pool shared by every installation of the app. Leafward gives your site a deliberately smaller hourly allowance and pauses rather than spending the commons. A paused run says so and resumes where it stopped — nothing is lost and nothing is rewritten.

If a screen fails to draw

Leafward catches its own rendering errors and shows the reason instead of a blank frame. Send a screenshot of that message: it names what arrived and where, which is normally enough.

If the frame is genuinely blank — no message at all — that is a different failure and worth reporting as such.

If a run stopped short

Open the run. It will say which of three things happened: it reached the hourly quota, a batch reached its time limit, or part of it never reached the queue. All three are resumable from the same button, and none of them rewrites a page that was already done.

What Leafward will not do

It will not re-apply a cascade on its own. If somebody edits the restrictions of a page you have cascaded from, Leafward reports that the subtree has drifted and leaves the decision to you. The nightly reconciliation sweep reports and never writes: a scheduled job has no user behind it, and writing on nobody's authority is not something this app does.

Reporting a security issue

Write to [email protected]. Please do not open a public Marketplace review for a security matter; you will get a faster answer by mail, and a fix goes out as a Forge deployment rather than as an upgrade your administrator has to approve.