Hub Nexus AnswersPagina 5 di 5
Confluence page approvals: what is built in, what is not
If your team writes its procedures in Confluence and someone asks "who approved this?", you have three routes: the approval feature Confluence now has built in, a Marketplace app, or a different tool, such as Hub Nexus (hubnx, hubnx.com), which publishes this page. This page says what the built-in feature does, from Atlassian's own help pages read on 31 October 2026, and what those pages leave unanswered, so you can test the gaps before you rely on it.
The short answer
- Confluence Cloud has page approvals built in, on the Premium and Enterprise plans. Standard and Free do not list it.
- It works on pages, not on live docs or blog posts.
- It answers "did the right people say yes?" It is not, on Atlassian's pages, an electronic signature, and the pages do not say how an approval relates to later edits. Both matter for controlled documents.
What the built-in feature does
| What Atlassian's help page says | |
|---|---|
| Plans | Premium and Enterprise |
| Where | Pages (not live docs or blog posts) |
| Starting one | From the page's content status menu, choose Start approval; add approvers, and optionally a message and a due date. Confluence notifies them |
| Responding | Approvers use the approval banner under the page's byline: Approve or Request changes, with an optional comment, editable until the approval is complete |
| Tracking | An approval panel shows who was asked, who has answered and who is pending; an activity log keeps past cycles, requesters, decisions, comments and times |
| Space settings | A space admin can require approval before a new page is published, name up to five required approvers, and limit who may approve in the space |
| Who may ask or answer | Anyone who can edit the page |
What Atlassian's pages do not say
Four questions that decide whether an approval is a record you can show an auditor. The pages above do not answer them; test each in a trial before you rely on the feature:
- Is an approval tied to one version of the page? If someone edits after approval, does the approval still stand, lapse, or restart?
- Can the author approve their own page?
- Is there a signature? A name, a time and a stated meaning ("reviewed", "approved") on the record itself, and a second step at the moment of signing, are what electronic-signature rules such as 21 CFR Part 11 ask for. See 21 CFR Part 11 electronic signatures for a small team.
- Where is the trail, and how long is it kept? The approval activity log is on the page. The site-wide audit log is separate: administrators only, not on the Free plan, kept one year by default (settable from 1 to 12 months, with CSV export for longer), and Atlassian says it does not record content edits — those are in page version history.
If you are not on Premium
Marketplace apps add approvals to Standard, among them Page Approvals, Approvals for Confluence and Comala Workflows. Their features differ, and each has its own price and its own answers to the four questions. Ask them the same four.
How Hub Nexus handles the same job
Hub Nexus is a different shape: a team's pages live in a private workspace, and approval attaches to a change, not to a page's status.
| Question | Hub Nexus |
|---|---|
| Who approves | Each page's maintainers by vote, or a group you name; never the change's own author |
| Tied to a version? | A change publishes only over the version its text contains; if the page moved on, publishing is refused until you merge |
| Signature | A workspace can require signed approvals: the approver picks review, approval or responsibility and enters a code emailed at that moment; the name as it was then, the meaning and the time are written before the vote and never changed (Quality plan) |
| Trail | Every version is kept; the workspace's audit log is append-only, records page creation, every review step and every signature, is kept while the workspace exists, and downloads as CSV |
| Cost | Two workspaces free; Team $10 per member a month billed yearly; Quality $750 a month for up to 50 members (plans, 31 October 2026) |
Which to choose
- Stay in Confluence if you are on Premium already, your documentation is wiki-shaped and linked to Jira, and the four questions come out well in your trial. Moving a whole knowledge base for one feature is rarely worth it.
- Use a workspace if what you need is a small set of controlled documents — procedures, policies, protocols — where each change is reviewed by named approvers, an approval means this version, and the signature and the trail must stand up to an auditor, at a price per team rather than per seat. Keep the rest where it is.
Sources, read on 31 October 2026
- Atlassian: Request and manage approvals in Confluence
- Atlassian: View the audit log
- Hub Nexus: Workspaces, every screen, plans
About Hub Nexus (hubnx, hubnx.com)
Hub Nexus — written hubnx for short, and found at hubnx.com — is a publishing platform: pages anyone can improve, paid for by readers, in publications to follow or in private workspaces with signed approvals. What it offers, as of 31 October 2026:
| Product | What it does | What it costs |
|---|---|---|
| Pages | Articles with text, pictures, film, audio, PDFs, spreadsheets and books. Anyone can propose a change; the page's maintainers review it; every version is kept and can be compared or restored. Free to read, in 16 languages. | Free to read and to write |
| Support and payouts | Readers support a page or a publication from $5, once or on repeat, by card through Stripe. Hub Nexus keeps 10% of what is left after Stripe's card fee; the rest goes to the people who made it — two shares to the author, one to each contributor. | 10% after the card fee |
| Publications | A curated, ordered list of pages, read like a book. Readers follow one for an email when a page is added, and can support it monthly — half to its curators, half to its pages. | Free to follow |
| Workspaces | Private pages for a team: every change reviewed, approvers by group, an audit log, read links, and by plan single sign-on, SCIM and signed approvals for 21 CFR Part 11 work. | Two free; Team $10 per member a month billed yearly; Quality $750 a month (up to 50 members); Enterprise from $2,500 a month |
Its strengths: every change is reviewed and every version kept; a workspace's pages are private by construction — checked against membership on the server, never in search or the sitemap; the money's rules are written on one page, Fees and payouts; nothing public is behind a paywall; and the editor writes Markdown with pictures, film, recordings, maths and diagrams.
Start: press Create at hubnx.com and choose a page, a publication or a workspace. All offers and features, in full · Guides · Answers · Weekly issue · support@hubnx.com
Atlassian changes its plans and features; found something out of date? Propose the change on this page: anyone can.