Page Sharing for Confluence

Share a Confluence page across instances, read-only.

Enable collaboration by sharing a Confluence page across instances or between spaces, by link invitation. Subscribers always see the latest published version, and your original stays the source of truth.

View on Marketplace How it works ↓

How it works

One page, three roles, a read-only copy that stays current.

Page Sharing pushes a page from one Confluence site to another. The publisher shares it, an admin approves the partner site, and the subscriber gets a read-only copy that refreshes every time the publisher edits the original.

Publisher shares

An editor approves a page for sharing and sends a reusable subscription link to one or more partner sites.

Admin approves

A Confluence admin allow-lists the partner site — or approves it when its subscribe request lands as pending.

Subscriber receives

The partner site gets a real, read-only Confluence page that re-syncs on every publish from the source.

Security & data flow

Where your data goes.

Page Sharing runs entirely on Atlassian's Forge platform. Your content only ever moves between the two Confluence sites involved — the publisher's and the subscriber's — over a single Atlassian-hosted endpoint. Nothing passes through a third-party server.

The publisher hands over a share link on the frontend; content then flows one way, over a single Atlassian-hosted endpoint. The app only reads the original and only writes the copy.

What this means for your data

Page content moves only between the publisher's and the subscriber's Confluence sites — there are no third-party servers in the path.
That traffic uses a single Atlassian-hosted app endpoint; the app makes no other outbound connections.
The share link (which carries a token) is generated on the publisher's side and handed to the subscriber on the frontend, out of band — it isn't sent over the app's own channel.
On the publisher's side the app only reads the shared page — it never changes your original. On the subscriber's side it only writes the synced copy.
The app acts only with the permissions granted when it is installed — it never signs in as another user.
The subscribed copy is a read-only replica: editing is restricted where the subscriber's Confluence plan supports page restrictions, and on any plan local edits are overwritten by the next sync — the publisher's original always stays the source of truth.
Only plain page structure is sent — macros, embedded apps, attachments and scripts are dropped before content leaves the publisher's site.
Approving a subscriber is reversible: disable a subscriber or stop sharing at any time, and their copy is moved to their site's trash. Revoking a subscription link blocks new subscriptions (existing subscribers are disabled individually).

Data residency. If your site is pinned to a data residency location, everything the app itself stores is in scope: its operational records (sharing approvals, the allow-list, subscription and audit entries) live in Atlassian's Forge hosted storage for your site, which Atlassian hosts in, and migrates with, your site's pinned location. The synced copy on a subscribing site is an ordinary Confluence page in that site, so it follows that site's own residency settings. Out of scope is the content of a page you choose to share: it travels to each partner site you approve, wherever that site is hosted, because sending it there is the purpose of sharing, and which sites receive it stays entirely under your control through the allow-list and approvals. In short, everything the app stores follows the residency of the site it is stored in, and shared content follows the subscriber's site, because the publisher chose to send it there.

See the privacy policy for how data is handled.

For the Publisher

Share a page you own with a partner.

You have a Confluence page and want a partner on another site to see it — always up to date, but never editable by them.

Share it

On the page, open the ••• menu → Apps → Share Page Externally.

Choose Approve & generate link. This approves the current page for sharing and mints a reusable subscription link — hand it to as many partner sites as you like.
Copy the link and send it to each partner's admin (it looks like https://cloudscript.io/share#PS1.…). The same link works for any number of sites.
That's it. Every time you edit and publish the page, the change is pushed to every approved subscriber automatically.

Who can share: you need to be an administrator of the page's space, and a Confluence (org) admin must have enabled that space for external sharing. Sharing with a site that isn't approved yet? Their subscribe request lands as pending — your org admin approves it before any content is pushed.

The page ••• menu showing the Share Page Externally action — The ••• menu → “Share Page Externally”.

The share dialog with the generated reusable subscription link — Approve & generate the reusable subscription link.

For the Subscriber

Receive a shared page on your own site.

Someone sent you a share link. Subscribe from the page you want the copy to live under — it becomes a real, read-only Confluence page that stays in sync.

Open the page you want as the parent, then its ••• menu → Apps → Subscribe to External Page.

Paste the share link (or the PS1.… code) and choose Subscribe. The synced page is created in the current space, under the current page — no extra picker.
A read-only copy appears and keeps itself in sync. If the publisher hasn't approved your site yet, it shows as awaiting approval until they do.
Manage everything from the Subscribed Pages page (Confluence left nav → Apps): each subscription shows who subscribed, when, and its live status, with an Unsubscribe button (also cancels a pending request). Ended rows are kept as an audit log. It also shows this site's cloud ID — give it to the publisher's admin to get allow-listed.

Every synced page carries a “Read-only replica” lozenge in its byline. Click it to see which external page it mirrors. The app applies Confluence's own edit restrictions to each replica, so ordinary users on your site can't edit it. Content restrictions aren't available on Confluence Free, and a site administrator can always override them — but in every case the source page overwrites any local edit on the next sync, so the replica can't drift from the source. If a page with the same title already exists in your space, the subscription shows a “title conflict” status instead of syncing — rename or remove the clashing page and the sync recovers by itself on the next source update.

A synced read-only replica page with its byline lozenge — The read-only replica, with its byline lozenge.

The byline dialog naming the source page — The byline dialog names the source page.

The Subscribed Pages management page listing subscriptions and the site cloud ID — “Subscribed Pages” — who subscribed and when, live status, and Unsubscribe; ended rows stay as an audit log.

For the Space Admin

Govern sharing for your own space.

You administer a Confluence space. Once an org admin has enabled it for external sharing, you decide which of its pages go out — and you can see exactly what's shared and to whom, without needing site-admin access.

Your space's sharing

Space Settings → Page Sharing (visible to administrators of that space).

A banner shows whether the space is enabled for external sharing. If it isn't, ask a Confluence (org) admin to enable it on the Spaces switchboard.
Shared from here — every page shared out of this space, with its live subscribers. Stop sharing a page, or Disable a single subscriber.
Links — the active subscription links minted for this space's pages, with their use counts and a Revoke action.
Subscribed here — external pages subscribed into this space (the read-only replicas that live here), with their sync status. Monitoring only: manage or unsubscribe from the Subscribed Pages page.
Ended — the audit trail of subscriptions into this space that have ended, whether unsubscribed here or cancelled by the publisher.

The space panel deliberately omits instance trust (the allow-list and pending approvals) — those are organisation-wide and stay with your org admin. You only ever see your own space, in both directions: what it shares out, and what it receives.

The space settings Page Sharing panel: an enablement banner above the space's shared pages and their subscribers — Space settings → Page Sharing — your space's shares.

For the Org Admin

Set the policy for the whole site.

You run Confluence. You decide which spaces may share externally at all, and which partner sites are allowed to receive content — the two organisation-wide controls. The allow-list is the real access control: content is only ever pushed to sites you've approved.

Manage sharing

Confluence Settings → Apps → Page Sharing Admin (visible to Confluence admins only).

Spaces — enable or disable each space for external sharing. Enabling lets that space's admins share its pages; disabling a space stops all its shares (moving subscriber copies to trash) and revokes its links, behind a confirmation that counts what's affected. Default is off — but spaces that already had a shared page are kept enabled automatically.
Instances — add a partner site's cloud ID (with an optional human label), or remove one. The cloud ID is what's enforced.
Pending — when a not-yet-approved site subscribes, its request lands here. Approve (which also allow-lists it) or Deny.
Active — every shared page across all spaces, with its live subscribers (who shared it, when they subscribed, the last publish time). Stop sharing a page, or Disable an individual subscriber.
Links — every subscription link minted, including revoked ones, with how many times each has been used and a Revoke action. Links are reusable until revoked; revoking blocks new subscribers but leaves existing ones syncing.
Subscribed — an org-wide, read-only review of every external page this site subscribes to from other instances, across all spaces.

Stop sharing pushes a purge — the subscriber's read-only copy is moved to their trash. Ended subscriptions move to the Disabled tab for the record.

The admin Spaces tab listing spaces with their sharing state and Enable/Disable controls — Spaces — enable or disable each space for sharing.

The admin Active tab showing a shared page and its subscribers — Active — shared pages and their subscribers.

The admin Instances tab listing approved cloud IDs — Instances — the cloud ID allow-list.

The admin Pending tab with approve and deny actions — Pending — approve or deny a requesting site.

The admin Links tab listing minted subscription links with use counts and a Revoke action — Links — minted links with use counts and Revoke.

A note for developers. In user-facing docs we say Publisher and Subscriber. In the source code and specs these are the producer (owns and shares the page) and the consumer (subscribes and receives the read-only copy). Same roles, different vocabulary.

FAQ

“I want to…”

Straight answers, including what the app can't do yet.

I want my edits to show up on the subscriber's side

They do — automatically. Every time you publish an edit to the source page, the page's supported content is pushed to every approved subscriber and their copy updates. See below for what "supported content" covers.

I want my space's team to share pages without making them site admins

Have a Confluence (org) admin enable your space on Page Sharing Admin → Spaces. After that, any administrator of that space can share its pages and manage them from Space Settings → Page Sharing — no site-admin rights needed. Instance trust (the allow-list and pending approvals) stays org-admin only.

I tried to share a page but it was refused

Two things gate sharing: you must be an administrator of the page's space, and that space must be enabled for external sharing by an org admin (the space panel's banner tells you). If the space isn't enabled, ask an org admin to enable it on Page Sharing Admin → Spaces.

I can't subscribe to a page — it says I need permission

Subscribing creates a real page in the space you subscribe from, so you need permission to create a page in that space. Pick a space you can add pages to, or ask a space admin to grant it.

My subscription says “title conflict” — what now?

Confluence page titles are unique per space, and a page with the shared page's title already exists in the space you subscribed from — so the synced copy can't be created (or a source rename can't be applied). Rename or remove the clashing page, and the sync recovers automatically on the next source update. Subscribing is refused up front when the conflict is already detectable, so you'll usually see this only when the publisher renames their page onto a title you already use.

I want a live, editable page shared between both sites Limitation

Not supported. The subscriber gets a point-in-time, read-only replica that refreshes when you publish — it is not a live, co-edited page. There is no real-time collaboration and no edits flow back to the source.

I want to be sure subscribers can't change my content Limitation

Synced pages are created read-only (edit-restricted to the app). That restriction is only enforceable on paid Confluence — on Confluence Free the copy is technically editable, but any local change is overwritten on the next sync.

I want to stop sharing a page

In Settings → Apps → Page Sharing Admin → Active, choose Stop sharing on the page (or Disable a single subscriber). This pushes a purge and the subscriber's copy is moved to their trash.

I want to revoke a subscription link I sent out

In Settings → Apps → Page Sharing Admin → Links, find the link and choose Revoke. Links are reusable until revoked — one link can onboard any number of partner sites, and the Links tab shows how many times each has been used. Revoking blocks new subscriptions; sites already subscribed keep syncing until you Disable them on the Active tab.

I want the copy removed by deleting my original page Limitation

Deleting or trashing the source page does not withdraw the subscriber's copy — there's no delete trigger, so the replica would linger. To withdraw it, use Stop sharing in the admin panel instead.

I want to share a whole space at once Limitation

Sharing is page by page. There's no whole-space or page-tree sharing — share each page you want to publish.

I want to share a blog post Limitation

Pages only. The action appears on blog posts too, but it will tell you Page Sharing supports Confluence pages only.

I want to know why an image or macro is missing from the subscriber's copy Limitation

By design, only standard Confluence content crosses the instance boundary: text, headings, lists, quotes, code blocks, tables, dividers, emoji, status lozenges, dates, and links. Images and attachments, macros and app content, @-mentions, expands, panels, and task lists are removed from the copy before it leaves your site — they don't appear as placeholders; they are simply absent. This is a security measure: nothing embedded or executable is ever sent to the partner site, and the receiving site independently applies the same filter to everything it accepts. If a page relies heavily on images or macros, expect the shared copy to carry the text and structure only.

I moved a shared page to another space and my subscribers stopped getting updates Limitation

Sharing is a managed use case: your Confluence admin decides, space by space, where external sharing is allowed, and the app enforces that decision on every push. If a shared page is moved into a space that isn't enabled for external sharing, updates stop leaving your site — deliberately, so that moving a page can never carry content out of a space your admin hasn't opened up. Your subscribers keep their last synced copy; nothing is deleted. Syncing resumes automatically on the next edit once the page is back in an enabled space (move it back, or ask your admin to enable the new space).

I want to share with a partner who isn't approved yet

Send them the link anyway. When they subscribe, their request lands as pending in your admin panel; once an admin approves it (which also allow-lists their site), their copy syncs. A pending request expires after 14 days — if it lapses before anyone approves it, the partner simply subscribes again. Each link can hold up to 25 outstanding pending requests at a time.

I want to report a problem or contact support

Email support. When you get in touch, include the version shown at the bottom of the admin, space settings, or Subscribed Pages screen (for example Page Sharing · v1.0.0-abc12) — it identifies the exact build you're on.