If you have a “template” which requires specific permissions and that template could be in use on multiple pages, security settings on the page level would not safeguard you against someone placing that view into another page and making it visible - unbeknownst to you. Said another way: if we had page-specific security settings in place, there’s nothing to stop another designer from placing the same views from a restricted PageA into PageB where PageB has no such security and therefore the views are visible to anyone.
View-scoped security is the only current way to securely restrict content across multiple pages/sessions.
There’s an option available:
I would recommend that in the View onStartup Event you make a check to see if the user meets your defined criteria, and if they don’t then you could request they login. There is a problematic scenario, however, in that if they are unable to ever enter credentials which would supply them the valid permissions then they would be trapped in an authentication cycle until they change the URL to navigate to a different page.
An alternative would be to open a Popup which describes why the View is unavailable to the user, and provide within that Popup a way to re-authenticate.