# Confluence - Ownership Scanner

> Identify Confluence pages owned by inactive users and restore clear ownership.

The Confluence - Ownership Scanner workflow automatically detects pages in Confluence that are owned by inactive user accounts. It helps teams uncover orphaned documentation, clarify responsibilities and maintain long-term documentation quality.

- Area: n8n Automation
- Type: Free
- Category: IT Operations
- n8n template: https://n8n.io/workflows/12238-scan-confluence-pages-with-the-rest-api-for-inactive-page-owners/
- Source: https://www.sus-tech.com/en/solutions/confluence-ownership-scanner

## Confluence - Ownership Scanner

Ensure clear ownership of your Confluence documentation by automatically identifying pages owned by inactive users.

### What this workflow solves
Over time, Confluence pages often remain assigned to users who have left the organization or lost access. This workflow identifies such pages and creates transparency around ownership gaps, enabling proactive cleanup and reassignment.

### Key features
- Detects Confluence pages with an **inactive owner**
- Uses **Confluence REST API v2** to retrieve spaces and pages
- Resolves page owners efficiently via the **users-bulk API**
- Generates a consolidated report including:
  - Page title
  - Owner email
  - Owner account status
  - Last updated date
  - Direct page URL
- Ideal for:
  - Documentation governance
  - Ownership and responsibility audits
  - Onboarding and offboarding processes

### How it works
- The workflow is started manually.
- Configuration is handled via a **Set Variables** node:
  - Atlassian domain
  - Space keys to scan
- Get Spaces (v2) retrieves relevant spaces and extracts space IDs.
- Get Pages (v2) fetches pages from those spaces.
- Two parallel paths run:
  - Pages are split into individual items.
  - Unique `ownerId`s are collected and resolved via bulk user lookup.
- Page data is merged with user data (`ownerId` ↔ `accountId`).
- Pages with inactive owners are filtered.
- Results are aggregated into a single `pagesWithInactiveOwner` array.

### Setup requirements
- Atlassian / Confluence Cloud account
- HTTP Basic Auth credential (email + API token)
- Optional extensions:
  - Email or Slack notifications
  - CSV or spreadsheet export
  - Pagination for large spaces

### Notes
- Pages are flagged if `accountStatus !== active`.
- The default page fetch limit is 50 items per request.

## Related blog posts

- [Why Data and Identity Governance Is Critical for Every Business - and Why Starting Early Matters](https://www.sus-tech.com/en/blog/why-data-and-identity-governance-matters.md)
- [Closing Access Gaps: The Role of Automation in Identity Governance](https://www.sus-tech.com/en/blog/the-role-of-automation-in-identity-governance.md)
- [Establishing Accountability: Automating Ownership Governance in Confluence](https://www.sus-tech.com/en/blog/establishing-accountability-automating-ownership-governance.md)

## Contact

Consulting and implementation: https://www.sus-tech.com/en/contact