Start here
What is yours, once you sign in
This screen is assembled from your role and your queue, not from a fixed home page. You are a requester, so it opens with 4 cards at headline depth and in read-only mode. Everything else in the product stays reachable from the left; it simply stops being the first thing you meet.
How deep this screen opens
Progressive disclosure is a product rule here, not a per-page decision. Your role sets the default; you can go deeper without changing anyone else's default.
Your role carries a stored default of headline. Read-only is derived from the role, not a setting. It is stated on screen rather than discovered by a failed click.
Waiting on you
Nothing in the single queue is routed to you.
Headline depth shows the figure and nothing behind it. Switch to working depth above to see the rows.
Routing is by remit. An item can be yours and still be one you are not permitted to sign.
Changed in the seven days to 17 August 2026
177 things happened in the seven days to 17 August 2026 across the queue, the decision record, escalations, questions and saved views.
Headline depth shows the figure and nothing behind it. Switch to working depth above to see the rows.
The product does not record when you last looked at it. What changed is therefore a fixed window - the seven days to 17 August 2026 - identical for everyone, and not a personal since-you-were-here list.
The estate you are looking at
14 functions, 154 sub-functions and 1,361 agents are modeled end to end.
Headline depth shows the figure and nothing behind it. Switch to working depth above to see the rows.
Every one of these is a modeled estate, not a survey of a real company.
Views colleagues saved
9 of 11 saved views are open to the role you hold, opened 65 times between them.
Headline depth shows the figure and nothing behind it. Switch to working depth above to see the rows.
A saved view stores a question or a filter, never a copy of the answer. Opening one runs the query again, so a link shared on Monday can legitimately show a different number on Friday. That is the intent.
What every other role opens with
No two roles open on the same set. This is the whole table, so nobody has to guess what a colleague is looking at.
| Role | Opens at | Mode | Cards | What it leads with |
|---|---|---|---|---|
| Enterprise Chief of Staff | Full | Can act | 8 | The whole estate, and everything waiting on you |
| Function Leader | Working | Can act | 7 | Your function, what it owes, and what is waiting on you |
| Process Owner | Working | Can act | 6 | Your processes, their exceptions, and the benefit not yet proven |
| Approver | Working | Can act | 5 | What is yours to decide, ranked, and who is covering you |
| Requester | Headline | Read-only | 4 | Where your work is, and what moved |
| Operator (legacy) | Headline | Read-only | 3 | Where your work is |
You are in read-only mode
A majority of the people whose adoption is being sought need to look and never act. That is a mode, not a limitation to work around.
Read-only is derived from the role on the account and is shown rather than hidden. It removes the ability to act. It does not narrow what can be read.
2 roles open read-only of 6, which is 33% of the roles on this estate. Read-only is derived from the role record, not from a preference somebody can toggle.
Actions
What is waiting on a person
This screen is the first thing a person meets, so the things it can get wrong are worth counting. Each line below is a property of the opening itself, not of the estate behind it.
cards separate the fullest opening from the thinnest
Enterprise Chief of Staff opens on 8 cards and Operator (legacy) on 3. That difference is the whole mechanism: subtraction by role, not a fixed home page with permissions hidden inside it.
roles can act from what they are shown
Enterprise Chief of Staff · Function Leader · Process Owner · Approver. Acting still runs through the single queue and is still refused by the authority register and the separation matrix; the opening changes what is offered, never what is permitted.
of the six roles open in read-only
Requester · Operator (legacy) can read everything the surface holds and act on none of it. The mode is derived from the role and shown on the screen rather than discovered when a button does nothing.
cards a role asks for that do not exist
Every card named by every role is built. 10 card builders cover all 10 cards the six roles ask for between them.
personal since-you-were-here lists exist
Nothing in the product records when an account last looked at a page. What changed is therefore a fixed window - the seven days to 17 August 2026 - which is the same for everybody who opens it. Calling that personal would be the easiest lie on the screen to tell.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
What the opening does. It selects and orders cards that already exist elsewhere and runs their queries live. It holds no figures of its own, so it cannot disagree with the page a card points at. What it does not do. It does not filter the estate. Every card is the same population the underlying page shows; only the arrangement is by role. Where the arrangement comes from. Six stored role openings, each naming its cards in order and its default depth, with 10 builders behind them. How acting works. The opening never writes. Every action on it is a link into the surface that owns the record.
Live observability
What the record shows right now
The 3 depths below partition all 6 role openings: each role has exactly one default. Depth is the level a surface opens at, not a permission - anyone can deepen any card, and nothing is hidden by opening shallow.
Current distribution
6 roles
Is policy and strategy coming to fruition
Whether the written intent is holding here
Partly
Nothing on the record settles this
The written intent is a product a person can use without being trained on it. What is now true: the first screen is derived from the role and the post, 6 roles have a defined opening, 2 of them open read-only and say so, and every card is a live query rather than a stored figure. What is not true: this is one screen of roughly eighty. The rest of the product still opens the way its author wrote it, and no measurement exists of whether anybody actually finds this screen easier - there is no usage telemetry in the product to measure it with.
What this page is, and what it is not
This screen is your role and your post arranged into one place. It is a different arrangement of the same records, not a different set of records, and nothing here is computed only for you.
Default depth is a property of the role, and this opening screen is the only surface that reads it. Every other surface in the product opens at the depth its own page sets, so the rule is stated here and honored in one place.
Every card your role asks for is built and rendering above. 1 card has nothing to list at any depth on this reading: Waiting on you. The figure is still shown; there is simply nothing behind it today.
The depth setting in the address bar changes what you see and nothing else. It does not change your role, does not change what anybody else opens with, and is not remembered between visits.