I don't know how to answer this... because it is not really related to the original question.
Route-level protection
The users who are authorized to visit URLs in your application is not defined at the View level, you would use the auth middleware to protect those routes. Similarly, you can use the can middleware (along with the associated gates and policies) to protect some routes from authenticated, but unauthorized users
View-level protection
Within a view template, you can conditionally render different parts of your view depending on a user being authenticated using the @auth or @guest directives as appropriate to your situation
@auth
// only visible to authenticated users
@endauth
@guest
// only visible to
@endguest
Similarly, whenever you have different permissions for authenticated users, you can use the @can directive to conditionally render parts of the view depending on the authenticated user being authorized.