what template permission should I set for non-content pages ?

[adrianmak]

For a big website, in PW contest, there might have many non-content pages.

Non-content pages are referring to those, log-in, log-out, register, store-check-out and etc

which are just a template container response to a front-end url path.

As an site content editor, these pages are not necessary to show at back-end with this user role.

These pages are meaningful to a site builder, site administrator

What roles should I set on these templates, so that they cannot be see by a content editor at back-end

[Martijn Geerts]

As those don't need custom content you probably can go for urlSegments instead of real pages.

[netcarver]

@adrianmak,

Have you taken any steps to try to solve this issue yourself?

[mr-fan]

URL segements are great you could create a own little routing with the different segements to your scripts (login, logout, register...)

But if you go the template way with a Adminbranch for example /app/  and subpages like /app/login/  you could take a look at this module from adrian:

https://processwire.com/talk/topic/11499-admin-restrict-branch/

regards mr-fan

[adrianmak]

I'll take a look of all the above suggestions.

Thanks anyway