As a rule, on sites that allow membership, you want to offer your users some data that is visible only when you log in.
For my site, if a registered user is the owner of the data, I want to offer some tools that allow them to manage the data.
My question is that. Do you share this responsibility between two different views? One view is loaded for "regular" users, and the other is loaded for "owner" users. The view that ordinary users see simply shows the data. The owner sees the data and some tools for managing it.
Or do you perform checks in one view and hide / show blocks inside it (similar to what you would do in normal ASP.NET)?
This may be a preference, but are there any technical reasons for sharing responsibilities between the two views and the only species?
source share