Restricting Frontend Resources by Web User Group in Evolution CMS

Evolution CMS already has the building blocks needed for frontend access control: web user groups, protected resources, and login components. Problems usually appear when one of those pieces is configured only halfway.

Core idea

• Put the web user into the right group.
• Mark the resource as protected for web access.
• Grant that resource to the matching group.

In many cases that is enough. If access still fails, the problem is usually not the idea of group protection itself, but the way the resource, login flow, or group assignment was set up.

What to verify

• The user is actually in the expected web group.
• The protected resource is linked to that same group.
• The login component is working against web users, not manager users.
• No custom redirect logic is bypassing the protected-page flow.

For classic Evo sites, this remains the cleanest pattern: keep access control in the CMS permission layer first, then add template behavior on top only if the UX needs it.