TL;DR
The problem: A hand-maintained project index page in Confluence goes out of date every time a project starts, closes or changes phase.
The fix: Tag every project overview page with shared metadata and build the portfolio menu from a query, so new projects appear automatically.
Filtering: The same metadata fields let portfolio leads narrow the view to, for example, only “At Risk” projects or one team’s projects.
Consistent pages: A fixed tab layout per project phase lets readers go straight to the phase they need instead of scrolling.
Attention signal: View analytics show which project overviews stakeholders actually open, so quiet projects get a follow-up.
A live Confluence project portfolio comes from tagging each project overview page with shared metadata (status, phase, owner) and building the portfolio navigation from a query on those tags. New, changed and closed projects then show up in the view automatically, without anyone editing an index page. Add view analytics, and you also see which projects stakeholders have stopped reading.
Why does a manual project index page in Confluence go stale?
A manual index page depends on one person hearing about every change. When a project starts, wraps up or moves to the next phase, the portfolio lead has to find out, then edit the list by hand. In a portfolio spread across several spaces, the index is often outdated by the time anyone reads it.
The second gap is attention. A static index tells you which pages exist, not whether anyone opens them.
| Manual index page | Metadata-driven portfolio view |
|---|---|
| Updated by hand for every change | Updates when a page is tagged |
| One flat list | Filterable by status, owner, phase |
| Team leads ask the PM to add links | Team leads tag their own page |
| No signal on readership | View reports per overview page |
How do you build a cross-space Confluence project portfolio?
Start with a shared metadata schema, then let navigation read from it. With Metadata for Confluence, you define fields such as project name, status, owner and phase, and embed them in the project overview template used in every project space.
SubSpace Navigation then builds a “Project Portfolio” menu from a CQL query on those fields. Because the menu is a query rather than a list of links, it always reflects what is tagged right now.
- Define the schema: project name, status, owner, phase.
- Add it to the template: every project space uses the same overview page template.
- Build the menu: a SubSpace Navigation menu driven by a CQL query for pages tagged as project overviews.
- Reuse the query: create sub-views such as “At Risk projects” or “Projects owned by Team X”.
What does this look like for a project manager and a team lead?
Take Lara, a project manager responsible for a portfolio, and Joanna, a team lead running one of its projects. Joanna creates her project overview from the template and fills in the metadata. Her page appears in the portfolio menu straight away, so she doesn’t need to ask Lara to add a link.
Lara opens the “Project Portfolio” menu and sees every active project across all project spaces. She filters by status to find projects marked “At Risk”, then opens one to check its current phase.
| Role | Goal | What changes |
|---|---|---|
| Lara – Project Manager | One up-to-date view of every project | No index page to maintain |
| Joanna – Team Lead | Her project visible without extra coordination | Tagging the page is enough |
How do you organize a project overview page by phase?
A project overview that grows over months becomes a long scroll. Navitabs’ Progress design lays out each project phase as a tab in a visual sequence, so each phase’s content has a fixed, predictable place, and readers go straight to the phase they need.
The Progress design is a page layout the author sets. It doesn’t read the metadata or act as a live status indicator. The machine-readable status and phase stay in Metadata, which drives the portfolio menu and its filters.
- Overview: goals, scope, key contacts
- Progress update: latest status and this week’s changes
- Risks & decisions: open risks and the decisions taken on them
How do you know which project overviews people actually read?
Viewtracker – Analytics for Confluence reports views and viewers per page and per space. Enable its reports across the project spaces, and the portfolio lead can see how many stakeholders recently opened each project overview.
If a project page has barely been viewed since its last status update, that’s a signal. Lara follows up with the project owner instead of assuming silence means everything is fine.
- Open Viewtracker’s content report for the project spaces.
- Sort the project overviews by views and last viewed date.
- Flag pages with low readership after a status change.
- Follow up directly with the project owner.
Key takeaway
Project portfolio visibility in Confluence isn’t a reporting problem. It’s a structure problem. Once every project overview carries the same metadata, the portfolio view maintains itself, scales as new spaces are added, and shows both the projects at risk and the ones nobody is watching.
The Meridian Knowledge Structure bundle brings Metadata for Confluence, SubSpace Navigation, Navitabs and Viewtracker together for this kind of setup. All four apps are available on the Atlassian Marketplace, or book a demo to see it in your own Confluence.
Frequently asked questions
Couldn’t find what you need?
Yes. Tag each project overview page with shared metadata fields such as status, phase and owner. A SubSpace Navigation menu built from a CQL query on those fields then lists every matching page, whichever space it lives in. New projects appear as soon as their page is tagged.
Yes. Because status, owner and phase are stored as Metadata fields, the same query can be reused to create filtered views. Typical examples are “At Risk projects only” or “Projects owned by Team X”. Portfolio leads get focused views without keeping separate lists up to date.
No. The Progress design is a page layout that the author sets to organise the project phases into tabs. It doesn’t read metadata or update by itself. Live, filterable status stays in the Metadata fields, which also drive the portfolio menu.
Use Viewtracker – Analytics for Confluence reports on the project spaces. They show how many people viewed each project overview and when it was last viewed. A page with almost no views after a status update is a cue to follow up with the project owner.