nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Look for a guidance on exporting our confluence space metadata for content inventory project

Nico Chen

Dear the community,

I’m currently working on a content inventory project for our Confluence spaces. The goal is to export all pages along with their metadata — including Page ID, Title, URL, Parent Page, Status, Created/Updated Date, Creator, Last Modifier, and Access Restrictions — to help us audit and update our knowledge base.

We’ve tried using the “Export Space as CSV” feature, but the resulting files appear to be system-level data tables (for import/recovery purposes) rather than a readable page list. This makes it difficult to extract the information we need efficiently.

Here I come up with two question:
1. Whether there’s an official or recommended method to export a structured page inventory?
2. Any permission or security considerations we should be aware of when using the REST API for this purpose? As I may not reach the certain permission, I'd like to share those steps to our IT sector for the support.

Our intent is to perform this as part of regular knowledge maintenance, not for migration.

Thank you

Best regards,
Nico

Accepted answers

All comments

Arkadiusz Wroblewski

Hello and Welcome to Atlassian Community @Nico Chen

Confluence administration → Data management → Space reports → Create report → Download

Download a spaces report | Confluence Cloud | Atlassian Support

API is also definitely the way to go.

In particular:

GET /wiki/api/v2/spaces/{id}

supports including labels, properties, permissions and role assignments.

There's also a separate layer for Export Permissions Export permissions data to understand access across your site | Confluence Cloud | Atlassian Support

Everything depends really on your needs and level of Granularity.

Best,

Arek🤠

Nico Chen

Thanks for the warm welcome, Arek

I have a few question, as I am neither space admin nor site admin, for both two solutions you've shared will be required at what level of permission to act? Will be grateful to know so that I can approach to the right person for the particular methods.

meanwhile, I am checking other article and found "export legacy content" may be help ? Do you have any idea about this function and does it work too?

Thanks again for your kind support and the prompt reply!

Kind regards

Nico

Marc -Devoteam-

Hi @Nico Chen

Welcome to the community.

For a space report, Space admin permissions are required.

To start using the API, the token needs to be scoped correctly and this depends on read access to a space.

So the user executing the API needs to have read access to a space, to get the information

Arkadiusz Wroblewski

For the Space reports I mentioned first, Atlassian requires you to be an app (Confluence), site, or organization admin. In your case you would need to approach one of your Confluence/site admins to generate that report for you.

The REST API is different.

For simply reading spaces, you don't necessarily have to be a site admin. The API works with the permissions of the account making the request so you can retrieve spaces that you yourself are allowed to view. GET /wiki/api/v2/spaces/{id}, for example, only requires permission to view that space.

Regarding the Legacy content export you found: yes, that functionality exists, but it serves a different purpose: reviewing Legacy Content coming from Migration.

I encourage you to cooperate with your Admin, as they also mostly know directly solution 😉

Aron Gombas _Midori_

@Nico Chen

You can export any arbitrary list of pages, blog posts to CSV using the Better Content Archiving app. I supports all the metadata you mentioned, except access restrictions. You can show/hide the columns on the UI, then the current view will be exported to CSV:

I hope this helps.

(Discl. this paid and supported app is developed by our team. Free for 10 users.)

Nico Chen

Thanks Aron for sharing this app, I definitely will take a look

Levente Szabo _Midori_

Adding to what Aron shared above, since you mentioned this is for regular knowledge maintenance rather than a one-off migration: the fields you listed (Status, Created/Updated Date, Creator, Last Modifier) are exactly the signals that go stale again the moment you close the spreadsheet. So I think the audit works best as something that lives inside Confluence, not something you re-run by hand every quarter.

I also wanted to expand on the export itself: the CSV Aron mentioned isn't the same kind of dump as Export Space as CSV. Each column explodes into the actual fields you're after: Title becomes Content URL, Content ID, Content type and Content title as separate columns, and Creator explodes into Creator ID, Creator name and the created date, same pattern for last updated and last viewed. It's built to be a readable page-level inventory, not a system table.

That report shown above is called the Content List inside Better Content Archiving and Analytics, and it doesn't have to stay a one-time export. It's also a live, filterable view you can open site-wide or per space, or drop onto a page as a macro backed by a saved CQL query, so the inventory itself can live on a Confluence page and stay current instead of getting rebuilt from a CSV every time.

On top of that, Better Content Archiving and Analytics keeps the underlying data current automatically:

Automatic status and expiration tracking, pages get flagged for review on a schedule you set, nobody has to open each page to update it.
Owner notifications, one consolidated email per owner listing everything of theirs that's due, instead of chasing people manually.
Archiving, reviewed pages get archived, or deleted, depending on your own document management practices, once a rule fires.

For a compliance or audit angle specifically, this is what turns a one-time cleanup into something repeatable you can point to later.

I'm also part of the Midori team, feel free to drop me a line at levente.szabo@midori-global.com if you want to walk through your specific needs.

Mia Tamm _Simpleasyty_

Hi @Nico Chen

This is a really interesting use case. Once you start treating Confluence as a content inventory, having the metadata in a consistent, structured form becomes almost as important as the page content itself.

The native export is useful for migration/recovery, but not really designed as a human-friendly inventory. I’d also be interested in whether you need only Confluence system metadata, or eventually custom metadata such as owner, business unit, review date, classification, etc.

Nico Chen

Hi the community,

I've been looking into the documentation, and it seems the "Space reports" focus more on high-level analytics rather than giving me a simple list of pages in the space. The "Legacy content report" actually looks a lot closer to what I need!

Basically, I am looking to export the data for a specific space, which should include:

Page Title
Owner
Creation Date
Last Modified
Content URL

I am wondering if anyone knows of any built-in tools or macros to support the need?

Besides, an AI assistant mentioned that Atlassian Support could generate a CSV file directly from the backend database if requested by a Site Admin. I would like to check if this is true and if there is any official documentation regarding this process?

Thanks again for the help!

Kind regards

Nico

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

metadata