An operator cannot archive, purge or reassign a wiki site from the console #72
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#72
Reference in New Issue
Block a user
What a person cannot do today
Act on a wiki site from the operator surface. Every site action the console offers (archive, restore, keep active, delete for good) is a member action, and each one checks that the site belongs to the signed-in member's workspace. The operator's wiki page is a read-only table with links out to the sites themselves.
Sites with no member owner are therefore unreachable from the console entirely: the farm's own root site, sites left behind by a removed member, and the sites the boot reconciliation parks in the holding workspace have no member whose workspace check could ever match. Freeing one of those names means reaching past the console into the farm's own admin tooling.
What they should be able to do
Archive, restore and permanently delete any site from the operator surface, and hand an ownerless site to a member's workspace.
Why it matters
A whole class of cleanup has no path through the product, and an operator who needs a name back has to use a tool the console does not present as part of running it.
Where
The operator wiki page under the integrations section, and the site handlers in that integration's web package, whose ownership check is the member's own.
Done when
The operator surface offers archive, restore and permanent delete for any site, guarded by the operator role; an ownerless site can be assigned to a workspace; and each action is recorded the way a member's own action is.
Migrated from status/issues.md at
b7a0e15