FAQ

Is Greenlight Published the same as Confluence Publish?

No. Confluence Publish makes the page content available in Confluence. Greenlight Publish means the approval cycle finished and review restrictions were cleared. You still use Confluence to author and publish content.

Do I need the Greenlight Approval macro?

No. It is optional. Use the byline (and the page banner when the macro is not present) for the same submit / approve / publish flow. The macro is handy when you want review controls visible in the page body. See Approval macro.

Why did the page banner disappear?

If the Greenlight Approval macro is on the page, Greenlight hides the banner on purpose so you are not shown two control surfaces.

Where did the macro go after Publish?

That is expected. When the owner Publishes in Greenlight, the app removes the Greenlight Approval macro from the page body and leaves a clean Published document.

Do I need Apps → Greenlight for every review?

No. Day-to-day work is from the byline (or the macro). Apps → Greenlight is for site defaults (page lock) and the pending approvals dashboard.

Why didn’t reviewers get notified?

If the Confluence page was never published, Greenlight queues notifications until first publish. Publish the page in Confluence, then check comments for @mentions.

Why didn’t the page lock?

Confirm lock is enabled under Apps → Greenlight, and that the space grants Add/Delete Restrictions. Edit permission alone is not enough. Confluence Free cannot apply page restrictions.

Can one reviewer approve for everyone?

No. In Standard, all assigned reviewers must approve. Any rejection returns the page to Rejected.

What is Advanced?

Advanced (coming soon) adds routing, teams, deeper restrictions, Jira stage tickets, Converse discussions, and more. Standard stays the reliable linear path.

Back to the Greenlight Standard overview →