Problem Definition

When a Service Account is deleted from the Atlassian Admin Hub, it is not automatically removed from Confluence Space Permissions or Page Restriction lists.

Unlike regular user accounts, which may be deactivated and reactivated, a deleted Service Account is permanently purged. However, the entry remains in the permissions UI (appearing as "Deactivated"), requiring manual cleanup by administrators.

Suggested Solution

Implement a process where deleting a Service Account from the Organization/Admin Hub triggers an automatic removal of that account from all:

• Space Permission lists
• Page Restriction lists
• Any other product-level permission schemes

Why this is important

• Clarity and Security: Retaining "Deactivated" entries in permission lists creates confusion for administrators and makes it difficult to audit who (or what) truly has access to content.
• Permanent Deletion: Unlike managed users, there is no way to recreate a Service Account with the same unique ID. Since the account can never be recovered or reused, there is no functional reason to retain its entry in permission lists.
• Administrative Overhead: In large organizations with many service accounts, manually auditing and removing these orphaned entries from hundreds of spaces is a significant manual burden.