Offboarding takes an afternoon
The inventory is produced for you. The reassignment is a plan you approve.
The work that eats the week
Reassignment, permissions nobody can explain, and content nobody has opened since 2023. Then the question of who owns what. All of it is manual.
Nothing changes until a person says so.
The AI reads, explains and proposes. Anything it suggests arrives as a card that routes into the same approval gate a person would use, with the same signature and dual-control rules. Publishing always creates a new copy and never overwrites your work.
Who owns this, and what breaks if they leave
One person leaving is not one action. Their workbooks, data sources, subscriptions, alerts and flows all have to be found and judged. Each one needs a new owner. The ones nobody claims break quietly a month later.
- Everything a person owns, in one list, before they leave
- Reassignment staged as a plan you approve, never applied quietly
- A record of what moved and who approved it
Content nobody has opened in a year
Every site gathers dashboards that still refresh and still cost extract time. Somebody still trusts them, and has not noticed they are stale. The job is quick to describe and slow to do by hand.
- Usage read from the site itself
- Certification and ownership shown beside the usage
- A person decides before anything is archived
Permissions you inherited from people who left
Most permission structures are layers left by people who have moved on. Few of them are written down. All of them are load-bearing until you prove otherwise.
- The permission as it resolves for a person
- The gap between what a group should have and what it has
- A change plan you can read before anything is touched
What changes
Stale content arrives as a list
Usage, ownership and certification, all on the same row.
Every change has a record
Who approved what, when, and against which version of the content.
Start with one site
Connect one Tableau site and run the inventory. Look at what comes back, then decide.