It's a house-keeping best-practice to keep Spaces owned by active users. This also prevents admin overload when end-users require something the Space owner can do but the owner is no longer in the company.

Currently in Confluence, there's no way to achieve this except by burdensome manual tasks.

The ask of this Feature Request is to implement Automation Rule Trigger, Branches and Actions — or something equivalent.

 

---

Full Scope

This is the best-case implementation.

New Trigger

User Deactivated (or "Space Owner deactivated")

New Branches

For each Space the user is owner of

New Action

Update Space Owner (User picker)

 

---

Partial Scope #1

This is a partial implementation but already helps Admins.

New Trigger

User Deactivated (or "Space Owner deactivated")

New Branches

For each Space the user is owner of

 

The Action would be to email or somehow notify Admins that Space Owners have been deactivated so they can take the respective actions.

 

---

Partial Scope #2

This is a partial implementation but already helps Admins.

New Trigger

User Deactivated (or "Space Owner deactivated")

New REST API or GraphQL endpoint

Provide an endpoint that can be called through the Web Request action and have the user passed as parameter. This endpoint would list All Spaces owned by the user.

The output would then be emailed or somehow notified to Admins so they can take proper action.

 

---

 

This is similar to CONFCLOUD-76513 and "For each page owned by a deactivated account" but it has been implemented for Pages and what's worse — PER SPACE — and requiring a Space selection. This is not useful at all for customers with hundreds of Spaces (typical of enterprise-level customers).