When using role-based permissions for Member page views, the Umbraco 13 backoffice provides a 'Restrict Public Access' popup, that lets you pick the groups with permission, but also forces you to choose a login page and error page. In my case (and I feel like, in many if not most cases) all pages that are restricted have the same login page and the same error page - Is there a way to set this globally (at least, for pages that have access restrictions) or do I really have to teach page editors to set it on each page being restricted?

All decendants will have the same restrictions applied to them so you would only need to set this at the top level

Fair enough! In the site I'm currently working on, many specific pages are permissioned, but not a clear 'all pages under this subtree' relationship

I would say that your use case isn't what @Matt Wise is mentioning, that's just by convention hierarchically all nodes under a protected node are also protected. maybe override here https://github.com/umbraco/Umbraco-CMS/blob/729016e429f9108639c33a00a33a93761e943da3/src/Umbraco.Web.Website/Routing/PublicAccessRequestHandler.cs#L43? but for distributed protected pages the backoffice ui is going to force you to choose a login/error page anyway, though I guess you could tell the editor to choose anything as it will be overriden?

🤔 Interesting. I didn't see anything relevant in the member registration documentation to this case, but always good to link to the documentation just in case 🙂 So I suppose my options here are: * Just leave it as-is, editors pick the 'login' page on each page individually, and I figure out a way to have the 'login' page redirect to the real login at my custom controller action, /auth/signin. * Figure out how to override PublicAccessRequestHandler's RewriteForPublishedContentAccessAsync method, probably switching out the switch case at line 105 for a 'redirect to /auth/signin' statement. Worried this will have side effects or require a bunch of attention to keep it working in future Umbraco updates. * Scrap the usage of 'Restrict Page Access' altogether and cobble together my own doctype property and override the renderController to boot you to /auth/signin if the user isn't allowed. Heavier initial lift, and similar to above I wonder how much of a lift maintaining the updated RenderController going forward will be, but surprisingly the least 'hacky' feeling answer.