Different column layout for summary page relation

What is the feature?

Consider Events, Users, and Registrations.
One Event can have many Registrations, one User can have many Registrations as well.

When looking at an event’s registrations, I would like to see the user as the first column since it’s a pretty important information.

However, when looking at a user’s registrations, well I don’t care about who the user is since we are in a user context and we already know. I would really like to see the event as the first column.

It would be nice to be able to change column configurations depending on the context (global listing vs record context). Something similar is available for segments, but sadly does not seem to apply to records.

I think I could hack something by defining two “Registration” collections, but I’d rather not.

What problem does this solve for you?

Having a neat, quick-to-analyze Summary page.
Being able to scan relationships visually way faster as well.

Who else would be using this feature?

Anyone with somewhat complex data structures and a need for visualizations.