Delegated admin tools
Give delegated admins only the tasks they own, as guided and reversible actions, and write the standard down so every module matches.
Why it mattered
Routine requests went through a central help desk, queues grew and delegated admins had no visibility. The platform’s native admin centers expose everything, so an admin who only needs to assign a number faces hundreds of options and real risk of breaking something tenant-wide.
Who we designed for
The branch administrator
Handles IT alongside other work. Wants to assign a number or fix a site today, without fear of breaking the tenant.
The telephony lead
Owns number ranges, policies and cost. Needs to see who changed what and prevent misassignment.
The governance lead
Cares about site sprawl, sharing and naming standards. Accepts delegation only with guardrails.
Where it got stuck
Simple changes waited behind complex ones in one queue.
No status or history visible to the requester.
Fear of the native admin center.
Each module worked slightly differently from the last.
The decisions
Show only what the admin owns
Scoping to the admin’s branch or site collection removes the fear of the whole tenant and shortens every list.
Review before commit
A read view mirrors the form grid, so what you see before saving is what you see after.
Destructive actions never in the command bar
Delete lives behind a modal that states the consequence.
Descriptions, not placeholders
Field help sits under the label so it stays visible after typing.
Skeletons over spinners
Skeleton loading for pages, spinners only for in-page actions, so the layout never jumps.
Write the standard down
Every rule carries its date and reasoning. Engineers build from it; new designers onboard from it.