Hi Dirksd,
Xperience by Kentico doesn't have a separate "gating plugin" you need to install - restricting access to pages is a native feature of the platform, built on top of the Members functionality and ASP.NET Identity.
Here's how it works in practice:
1. Set up member registration/authentication
Before you can gate anything, your site needs member registration and sign-in configured. This is standard ASP.NET Identity work that Xperience integrates with out of the box.
Registration and authentication
2. Gate a page from the admin UI
Once that's in place, go to the page in your website channel → Properties → Membership access, tick "Requires authentication", and optionally pick specific member roles if you only want certain groups (e.g., "Premium") to see it. Publish the change and it's live — no custom code needed for this part.
Secure pages
3. Member roles (if you need role-based gating, not just "logged in vs not")
Roles are managed through ApplicationRole / RoleManager, so a developer can create roles like "Premium" or "Partner" and assign members to them. You can also enforce roles on custom controllers/endpoints with the standard [Authorize(Roles = "Premium")] attribute.
Authorize using member roles
4. Same approach works for reusable content items
If you're gating something in Content Hub rather than a page, the same role-based restriction is available there too.
Content items – Secure content items
so no plugin needed, it's built in - but it does assume you've already got member registration/login wired up on the site. If that part isn't in place yet, that's the piece your dev team would need to build first, everything after that is configuration.
Hope that helps!