Since migrating to confluence cloud the 'Export' option on our pages is no longer available. When I click the three dots in the right top corner - there is no Export option
You are lacking the Export space permission that is being defined with roles in Confluence. Speak to your space/Confluence admin to grant you this permission.
Hi, I am once of the admins of the space but still no option
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even though you have the Admin role, if these checkboxes are not ticket, you still won't be able to export it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ellanor Hall_ Vodafone, the Export space permission won't be what's biting you. Atlassian puts the caveat inside that permission's own definition: it covers whole-space export, and at page level "anyone who can view a page or live doc can also export it". You can open the pages, so page export isn't gated on a space checkbox, which is why being a space admin changed nothing.
On the org policy angle, there is a way to confirm it from your own seat. The data export control blocks the page Export to PDF and Export to Word items, and in the same list, "the options to export to CSV, XML, and PDF" from a space's settings. So open Space settings on that space and check whether the CSV, XML and PDF space exports are still offered. Gone too? That's the policy. Still there and you're looking at something else.
That control is org-admin only, at admin.atlassian.com under Security, Data protection, Data security policy. A space or Confluence admin can't reach that screen, which is where the permission trail runs out. It's a Guard Standard control, and Guard Standard is included with Cloud Enterprise, so it's available to your org even if nobody bought Guard separately.
Docs rather than your tenant here, so the space settings check is the bit that settles it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
*This is related to Atlassian Guard rather than Confluence
On top of what Nikola said, and since you're on the Enterprise plan, you could check with your Atlassian Organization admin if they have set/enabled data classification and/or data security policies on organization level. 🔐
Those could also 'affect' the export option on specific spaces or pages/content.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you - I think it may be this issue, I will contact the org admin to see if this can be changed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ellanor Hall_ Vodafone , @Nikola Perisic is right that permissions are the first place to look, so let me add the detail that decides which admin has to click what, because there are two different exports and they are governed differently.
Single page export (the ⋯ menu on a page) needs only the ability to view the page. Per Atlassian's space permissions documentation, page or doc level export is governed by View: anyone who can see a page can export it. The separate Export permission (a space permission, and under role based access it lives inside the roles your space admin assigns) governs exporting a whole space from Space settings. So if the option is missing on individual pages you can otherwise read, a space permission is unlikely to be the cause.
On an Enterprise site, the switch that removes page export is usually the org data security policy. In Atlassian Administration (Security, then Data protection, then Data security policy) the data export control can be set to block for chosen spaces or classification levels, and when it is, the export option disappears from menus (recent changes also block attachment downloads under the same rule). A migration into an existing org, or a policy created since, is exactly when people first meet it. Ask an org admin to check that control and its overrides for your space, and whether the pages carry a classification level that a rule targets.
Fast way to tell which one you have: if a colleague with the same view access also lacks the option, or export is missing across every page in the space, it is the policy; if it is you alone, it is space access or role. Either way the fix sits with an org admin (policy) or a space admin (role), and now they know which door to open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.