Summary

Confluence already supports transferring ownership of pages, live docs, whiteboards, databases, and Smart Links — both via the UI and (for pages) via the REST API v2 PUT /wiki/api/v2/pages/{id} ownerId field. There is currently no equivalent capability for custom‑content items created by Connect/Forge apps.

As a developer, we need to programmatically reassign ownership when the original creator is deleted or deactivated.

Use case

• Lifecycle management of app‑created custom content when employees leave/are deactivated.
• Avoiding orphaned content owned by deactivated principals.
• Parity with the behavior already available for pages/live docs/whiteboards/databases.

Required behavior

1. Space admins and site/org admins can reassign ownership of any custom‑content item in their scope, including when the current owner is deactivated/deleted (mirroring page‑ownership rules).
2. The previous owner is recorded as lastOwnerId.
3. Standard notifications/audit log entries are produced, consistent with page ownership transfer.
4. Honors the same permission/access checks that the page ownership transfer endpoint uses (e.g. new owner must have access; otherwise return a recognizable error code).
5. Available in OAuth 2.0 (3LO), Forge requestConfluence/AGG with appropriate scopes.