Monitoring
Saved console layouts
Arrange a screen the way you read it, and find it that way tomorrow.
Layout is stored per user and per screen. Rearrange a view and it stays that way for you, on that screen, without changing what anybody else sees.
The per-person half is the point. An agency lead scanning for problems and an analyst reading one experiment want genuinely different things from the same screen, and a shared layout means one of them rebuilds it every morning or gives up and works around it.
It is per screen rather than global for the same reason. The arrangement that makes the roster readable is not the arrangement that makes a results table readable, and a single preference applied everywhere is a preference that fits nowhere.
A layout is a preference rather than data. Nothing about a result depends on it, so a saved layout that goes missing costs you a rearrangement and nothing else.