Magento 2 CMS page for logged-in customers: control access by customer group
SKU: CMSPAGERESTRICTION1
- Access per CMS page and CMS block: everyone, logged-in only or selected customer groups
- Free redirect targets with return to the requested page after login
- Restricted pages with noindex and excluded from sitemap and search
- Exception list and store-view control for multilingual shops
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 CMS page for logged-in customers: control access by customer group
With this extension you set up a Magento 2 CMS page for logged-in customers: dealer price lists, partner information, download pages or internal guides are visible only when a customer has signed in or belongs to a specific customer group. You define the rule right in the CMS editor, with no programming and no second system.
Magento ships without any access restriction for CMS content. Anyone who wants a closed area usually falls back on hidden URLs or server-level password protection. Both are inconvenient, not tied to your customer accounts and untidy from a search engine point of view. The CMS Page Restriction module solves the task inside Magento and Hyvä: access rule, redirect, notice text and noindex from a single source, set up by Mironsoft.
Closed areas with a Magento 2 CMS page for logged-in customers, without a second CMS
Decide who may see a CMS page or block: you set up the Magento 2 CMS page for logged-in customers right in the page editor, with clear rules for every other visitor.
Access per page
In the CMS page editor choose: everyone, logged-in customers only or selected customer groups.
CMS blocks too
Single blocks, such as a price list teaser, can be limited to customer groups as well.
Redirect with return
Locked-out visitors land on the login page and return to the requested page after signing in.
noindex for restricted pages
Protected content stays out of search engines, the sitemap and the internal search.
Exception list
Imprint, privacy policy and other pages always stay reachable, whatever else is set.
Per store view
Rule, notice text and redirect target can differ for each language and store view.
Use cases: when a Magento 2 CMS page for logged-in customers makes sense
Wherever a Magento 2 CMS page for logged-in customers is needed because content is not meant for every visitor but should still be maintained in the shop CMS.
Dealer area in a B2B shop
Wholesalers see tier conditions, catalog PDFs and dealer news while consumers do not see the page. The customer group "Wholesale" is enough as the key for a dealer area in Magento 2.
Partner and agency portal
Sales partners find logos, product data sheets and terms on protected CMS pages that you maintain like any other page.
Staff and internal area
Order policies, team discount codes or notes on handling returns live in the shop but only for logged-in accounts of an internal customer group.
Early information for regular customers
News and promotions appear first for a loyal-customer group. Anyone not signed in is guided to log in or to an explanation page. That is a Magento 2 CMS page for logged-in customers without extra tools.
How a Magento 2 CMS page for logged-in customers controls access right in the editor
Every CMS page and CMS block editor gets an extra "Access" section. There you choose whether the content is visible to everyone, to logged-in customers only, or to specific customer groups such as "Wholesale" or "Partner". No separate permission manager, imports or extra menus are needed.
- Three modes: Everyone, Logged in only, Selected customer groups
- Multi-select of customer groups, including "Not logged in"
- Same logic for CMS pages and CMS blocks
Redirect and notice: what visitors see when a Magento 2 CMS page for logged-in customers is locked
When someone without permission opens a protected page, you decide what happens: redirect to the login page, to the home page, or to any CMS page, for example an explanation of dealer access.
An optional notice message can be shown as well. After login the module returns the customer to the page originally requested, provided the account belongs to an allowed group.
- Redirect target global and overridable per item
- Notice text per store view, multilingual
- Return to the requested page after login
Restricted also means: out of the search index and never mixed up in the cache
Protected pages should not show up in search results. The module adds noindex/nofollow to restricted pages, removes them from the XML sitemap and hides them from page search. The redirect stays temporary (302), so the page can be opened up later without SEO leftovers.
The check respects the full-page cache: pages with a rule are served separately per customer group, so nobody accidentally receives another visitor's version.
- noindex/nofollow and sitemap exclusion applied automatically
- 302 redirect instead of a permanent one
- Cache separation by customer group
Closed area: without and with CMS Page Restriction
The Magento 2 CMS page for logged-in customers compared directly with the usual workarounds.
| Aspect | Without module | With module |
|---|---|---|
| Access rule | Hidden URL or server-level password | Choice in the CMS editor: everyone, logged-in only or customer groups |
| Customer groups | Not taken into account | Multi-select including "Not logged in" |
| Visitor without permission | Error page or browser password dialog | Redirect to login or a CMS page with notice text |
| Search engines | Page may get indexed or stays hidden by luck only | noindex, nofollow, no sitemap, no page search |
| Multilingual | Secure each language separately | Rule and notice text per store view |
| Maintenance effort | Developer or server access needed | Editors work in the familiar editor |
How the Magento 2 CMS page for logged-in customers is set up
The module is not downloaded: we set up the Magento 2 CMS page for logged-in customers in your shop. The process:
-
1
Clarify the need
We discuss which CMS pages and blocks are to be protected and which customer groups get access.
-
2
Installation in the shop
We install the module in your Magento 2 instance, first in a test environment if you wish.
-
3
Define rules and texts
Redirect target, notice text per store view and the exception list are configured together.
-
4
Test with two accounts
We check the pages as a guest, as an ordinary customer and as a member of the released group, including cache and search engine tags.
-
5
Handover
Your team receives a short guide on how to protect new pages and blocks.
Scope compared with other Mironsoft modules
CMS Page Restriction protects individual CMS pages and CMS blocks and so delivers the Magento 2 CMS page for logged-in customers. A shop-wide login requirement for catalog and checkout is a different task and is covered by the separate Force Login module. Approving new customer accounts is handled by the Customer Approval module, customer-group-dependent prices by Custom Price.
The modules can be combined: first you approve an account, then assign it to a customer group, and the dealer then sees their area. You need no separate password protection for that.
No download — personal setup instead
CMS Page Restriction is not listed here as a ready-made download for self-installation. The purchase is a service commission: after the purchase we get in touch, set up the Magento 2 CMS page for logged-in customers in your shop and agree with you which pages, blocks and customer groups are to be protected.
Frequently asked questions
On access rules, search engines, cache and how the purchase works.
How can I show a CMS page only to logged-in customers in Magento 2?
Can I protect single CMS blocks and not just whole pages?
What does a visitor without permission see?
Are protected pages indexed by Google?
Does it work with the full-page cache?
How can I release a CMS page for one customer group only in Magento 2?
Is a Magento 2 CMS page for logged-in customers GDPR compliant?
How long does setup take?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 CMS page for logged-in customers – Mironsoft CMS Page Restriction