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

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

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:

1. Automatic status and expiration tracking, pages get flagged for review on a schedule you set, nobody has to open each page to update it.
2. Owner notifications, one consolidated email per owner listing everything of theirs that's due, instead of chasing people manually.
3. 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.

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

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

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 😉

Hi Marc,  

Thanks for the adding some points, it's really helpful!

Hi Arek,

Highly appreciated for response, and yes, as you mentioned about Legacy content export, I could export the report format that I expected but few pieces only :(. I would take your suggestion and cooperation with our admin!

Thank you again!

Kind regards

Nico