48.3k Log in Get started
Dashboard

What does a knowledge-base health dashboard show in Metabase?

A knowledge-base health dashboard shows whether important content is current, owned, complete, and used. It combines content metadata from tools such as Confluence, SharePoint, Notion, Coda, Box, and Dropbox in one governed view.

For: Knowledge managers, operations, enablement, security, and program owners. Grain: one content item plus a required-topic inventory and optional activity events.

Which cards belong on a knowledge-base health dashboard?

  • Freshness rate and content by age bucket
  • Ownerless content by space, site, folder, or workspace
  • Knowledge-base coverage by required topic group
  • Stale high-priority content with owner and last review
  • Workspace activity rate with quiet and declining areas
  • External sharing or permission risk where the source exposes it

What data does the dashboard need?

  • content_items with stable ID, type, container, owner, lifecycle, created, updated, and reviewed dates.
  • required_knowledge_topics mapping operational topics to canonical content.
  • Optional content_activity_events for views, edits, comments, sharing, and contributor trends.
  • A freshness-policy table by content class, criticality, or audience.

How do you build it?

  1. Sync content metadata and versions into a database or warehouse.
  2. Normalize sites, spaces, folders, boards, and docs into containers and content items.
  3. Join the required-topic inventory and apply freshness windows by content class.
  4. Build summary cards, drill-through cleanup tables, and owner/container filters.

Example card SQL

Healthy content by containerPostgreSQL
SELECT
  container_name,
  COUNT(*) AS active_items,
  COUNT(*) FILTER (WHERE owner_id IS NULL) AS ownerless_items,
  COUNT(*) FILTER (
    WHERE last_reviewed_at < CURRENT_DATE - INTERVAL '90 days'
  ) AS stale_items,
  ROUND(
    100.0 * COUNT(*) FILTER (
      WHERE owner_id IS NOT NULL
        AND last_reviewed_at >= CURRENT_DATE - INTERVAL '90 days'
    ) / NULLIF(COUNT(*), 0),
    2
  ) AS healthy_content_rate
FROM content_items
WHERE archived_at IS NULL
GROUP BY container_name
ORDER BY healthy_content_rate ASC;

Metrics

Documentation freshnessKnowledge-base coverageWorkspace activity rate

Integrations

Confluence + MetabaseSharePoint + MetabaseCoda + MetabaseBox + Metabase

FAQ

Can updated_at stand in for a review date?
Use it as a fallback, with a caveat. Formatting, bot syncs, and metadata changes can update a record without validating its guidance. A deliberate last-reviewed field is stronger.
Should low-activity content be deleted?
Not automatically. Stable reference content can be valuable and quiet. Use activity to prioritize review, then check criticality, search demand, links, and ownership before archiving.