Trash and permanent deletion
Trash merges soft-deleted content and media into one surface, and Empty Trash has two blast radii — one site for siteAdmin, every site for superAdmin.
Trash merges two different soft-deleted sources into one list — deleted content and deleted media — and both sit behind the same authorization threshold, site admin, even though they're fetched from two different places under the hood. What actually lands in trash, versus what deletes immediately with no recovery at all, is covered from the content side on Trash and recovering deleted work; this page is about scope and permanence — what emptying trash actually reaches, and who can reach how much of it.
Site-scoped and global are different actions
Emptying trash for the site you're working in needs only site admin, and it only ever touches that site's rows. Emptying trash across every site on the install at once — every deleted page and every deleted media file, everywhere — is a separate action, gated to super admin specifically. The same split applies to just looking: listing one site's trash is a site-admin route; listing every site's trash in one call is super-admin-only.
Restoring or purging one item stays inside its own site
Acting on a single trashed item — restoring it or deleting it for good — is scoped to whichever site the request resolves to. An id alone isn't enough to reach across sites: an admin who could otherwise manage a different site's content still can't restore or purge a specific row there unless that site is the one the request actually resolved to.
What permanently deleting an item actually removes, and what it leaves dangling behind it, doesn't change with who's allowed to trigger it — see Trash and recovering deleted work for that detail.