Documentation

Last updated: 1 November 2026

Every Confluence Cloud user gets a personal space, often the first time they open Confluence — whether they ever use it or not. After a few years a site holds hundreds of empty personal spaces and spaces of people who have left, cluttering search and the space directory. Vacancy finds them and archives them safely.

1. Install

A Confluence site administrator opens Apps > Explore more apps, searches for Vacancy and selects Get app (or Try it free).
Review the requested permissions and confirm. No configuration is needed.
Open Confluence administration (gear icon) and choose Vacancy in the apps section.

2. The three flags

Untouched	The space holds only what Confluence created by itself: every page is still at version 1 and was created within two minutes of the space; there are no blog posts; no attachment or comment was added later; nothing other than pages (whiteboards, databases, folders, smart links) sits below the home page; at most 25 pages. Confluence's own sample page and its image count as automatic.
Owner left	The owner's Atlassian account is deactivated or deleted (Confluence's account status).
Dormant	No page or blog post changed for D days (default 365; change it at the top of the list).

3. Archive

In Personal spaces, filter or search, and select spaces. Untouched and owner-left spaces are pre-selected; you can change the selection freely.
Press Dry run: the job checks every selected space again and reports what would be archived. Nothing changes.
Press Archive selected and type ARCHIVE. The job runs in the background; you can stop it.

Archived spaces stay in Confluence exactly as they were. They no longer appear in search, the space directory or quick navigation, and can be restored at any time. Each space is read again right before it is archived; spaces that are no longer personal spaces or are already archived are skipped.

4. Restore and undo

On the Archived tab, select spaces and press Restore selected. In the history, Undo restores exactly the spaces that run archived. Restoring works also when the license is not active.

5. Daily rule and history

In Daily rule & history, turn on "untouched spaces created more than N days ago" and/or "spaces whose owner left, unchanged for M days" (at least 1 day each). Confluence does not record when an account was deactivated, so the owner-left part uses the space's last change. Dry run the rule now shows what it would archive today. The rule only archives — it never deletes — and runs only while the license is active. The last 30 runs are listed with a report you can copy as CSV.

Permissions

Only Confluence administrators can open Vacancy, start jobs or save the rule; every request is checked on the server.
Jobs run as the app, so the daily rule works without anyone signed in.
Scopes: read:space:confluence (list personal spaces), read:page:confluence and read:blogpost:confluence (count content, last change), read:attachment:confluence, read:comment:confluence and read:hierarchical-content:confluence (the "untouched" check: attachments, comments, whiteboards and other items), write:confluence-space (archive and restore spaces), read:confluence-user (administrator check and owner account status), storage:app (rule settings and run history).

Limits

Confluence Cloud only. Personal spaces only; team (global) spaces are never changed.
Vacancy archives and restores. It does not delete spaces, move content, change owners or permissions, or stop Confluence from creating new personal spaces (use Confluence's global permission "Create personal space" for that).
One job runs at a time.
When the license is inactive (for example after the trial), the list, dry runs and restoring keep working; archiving and the daily rule are off.

Need help?

See the support page.