Stop Seeing Double: Space & Label Filtering Is Finally Here for Metadata Reports

[#1]

Hello there!

I'm Elena from Elevatic. 

Do you know how Space and Label filters in the Metadata Report Macro put you back in control of what shows up in your reports and what doesn't?

Picture this: your team has spent months carefully structuring your Confluence instance. Drafts live in one space. Approved, published pages live in another. It's clean. It's intentional. It's exactly how it should work.

Then you open a Report Macro and see every page twice.

The draft. The published version. Side by side. Identical titles. No way to tell them apart at a glance, and no obvious way to filter one out. You've built the perfect documentation workflow, but your reports don't know that. To them, content is content.

That changes today.

The Problem with "All Content, All the Time"

The Report Macro has always been powerful. It pulls together content from across your Confluence instance based on content categories and metadata values, giving teams a dynamic, always-up-to-date view of their work. But that breadth came with a cost: no easy way to tell it where to look, or more importantly, where not to.

For teams running simple, single-space setups, this was fine. For everyone else—organizations with mature governance workflows, compliance frameworks, or quality management systems—it was a persistent friction point.

While every team structures Confluence differently, two common reporting patterns stand out across customer environments. These examples show how Space and Label filters can support real-world workflows, while leaving room for teams to apply them in ways that fit their own processes.

Use Case: Cleaner Reporting Across Distributed Content

For many teams, especially in regulated environments, the challenge is not creating content, but reporting on the right content.

In practice, teams often manage documentation in one of two ways:

• Space-based workflows, where draft content lives in one space and approved content is copied or moved into another

• Label-based workflows, where content can live anywhere, but labels like approved, published, or final determine what should count

Both approaches are valid. Both are common. And both create the same reporting problem:

Without the right controls, reports include content that should not be counted, such as duplicate pages, draft versions, or work-in-progress documentation.

The result is familiar:

• Inflated page counts

• Duplicate entries

• Drafts appearing in formal reports

• Reduced trust in reporting accuracy

This is where Space Filter and Label Filter work together.

Teams can now define reporting rules that reflect how their content is actually governed:

• Use Space Filter to include only the spaces that matter (for example, excluding draft or review spaces)

• Use Label Filter to include only pages that meet the required status (for example, approved or published)

These two features enable alignment of reporting with real operational workflows, whether governance is driven by structure, metadata, or a mix of both.

That means teams can build reports that reflect what is truly valid, current, and intended for visibility, without manual cleanup or post-processing.

Real-world impact

Compliance and quality dashboards reflect only valid documentation

• Leadership reports show true published output, not drafts or duplicates

• Teams can trust that reports reflect reporting rules, not just raw page volume

This is one practical example of how Space Filter and Label Filter can work together to improve reporting accuracy.

Depending on how teams manage governance, approvals, and publishing, there are many other ways these two features can be used to support cleaner, more reliable reporting.

You can combine both filters to precisely define your dataset:

“Only pages in the Compliance space AND labeled approved”

“Only Engineering space content with published label”

This gives teams fine-grained control over exactly what their reports represent.

Try Metadata for Confluence for free.

Who This Helps Most

If your Confluence setup looks anything like this, these filters are built for you:

• Quality Management Teams. Multi-stage approval workflows with formal publishing rules.
• Compliance & Governance. Audit-ready documentation that shows only approved content.
• Large Enterprises. Multiple teams, multiple spaces, and a need for scoped, trustworthy reporting.

How is this feature working for you?

Your experience shapes what we build next. Share your thoughts — it takes less than one minute.