Role/IP Restrict

Role/IP Restrict

89,00 €

Powerful access control for WordPress. Restrict any page, post, or the entire site by user role, login state, IP address, or named IP pools. Ideal for private areas, client portals, intranets, extranets, project pages, membership content, staging and test sites, and any environment where controlled access is required.

GUARANTEED SAFE CHECKOUT
  • Visa Card
  • MasterCard
  • American Express
  • Discover Card
  • PayPal

Description

Why Role/IP Restrict?

Many WordPress sites need to show specific content only to certain groups — employees, clients, partners, logged-in users, or even specific locations/IP ranges. Role/IP Restrict gives you granular visibility control without heavy membership plugins or complex setup.

The plugin lets you restrict:

  • Individual posts and pages

  • Entire sections of the site

  • Any content block inside the Gutenberg editor

  • Or the entire website with one global rule

All restrictions work server-side, ensuring that hidden content never appears in frontend HTML.

Perfect for These Use Cases

🔐 1. Intranets & Staff Areas

Restrict internal materials, HR documents, schedules, onboarding guides, instructions, and sensitive pages so they appear only to logged-in employees or specific roles.

🧑‍💼 2. Client Portals & Project Pages

Provide selected clients access to:

  • Project updates

  • Deliverables

  • Documentation

  • Timetables & reports

Use allow-lists to make pages visible only to the targeted user groups.

🌐 3. Extranets & Partner Networks

Share files or resources with external partners, vendors, or subcontractors.
IP pools allow easy restriction to:

  • Office IP ranges

  • VPN ranges

  • Country-specific subnets

🏗️ 4. Staging, test & development sites

Restrict the whole site with one global gate:

  • Allow only your team’s IPs

  • Allow only logged-in users

  • Prevent search engines from ever reaching the site

🔒 5. Private Membership Content

Instead of full membership plugins, create lightweight protected areas:

  • Premium articles

  • Paid content

  • Subscriber-only content

  • Member benefits

🛡️ 6. Controlled Access for Public Sites

Hide selected sections from:

  • Guests

  • Search engines

  • Specific roles

  • Known IP ranges (security / abuse prevention)

🗂️ 7. Multi-tenant or multi-department content

Create separate access zones based on:

  • Departments

  • Teams

  • B2B client groups

  • Editorial roles

Who Is This Plugin For?

  • Agencies managing client sites

  • Companies with internal/external user groups

  • Organizations with intranet content

  • Businesses needing IP-based access control

  • Developers needing a lightweight, reliable visibility tool

  • Anyone wanting content protection without a full membership system

The Result

A secure, flexible access-control layer that blends seamlessly into WordPress — without bloat, without complexity, and without performance impact.

Lieska Role Ip Restrict v2.2.3
2.2.3
Ensimmäinen julkinen versio

Reviews

There are no reviews yet.

Be the first to review “Role/IP Restrict”

Your email address will not be published. Required fields are marked *

✅ Role/IP Restrict – Installation & User Guide (EN)

1. Installation

A) Upload & activate

  1. Go to WordPress Admin → Plugins → Add New

  2. Click Upload Plugin

  3. Select the ZIP file

  4. Click Install Now

  5. Click Activate

After activation, you will automatically be redirected to the License tab.

2. Licensing

  1. Open Settings → Lieska Plugin Licenses

  2. Locate Role/IP Restrict

  3. Enter your license key

  4. Click Save License

A valid license enables:

  • Automatic updates

  • Security fixes

  • New features while the plugin remains in active development

3. Features Overview

Role/IP Restrict includes three complementary restriction systems:

A) Per-Post Restrictions

Set rules for individual pages, posts, CPTs.

B) Global Gate (site-wide restriction)

Protect the entire site with one rule.

C) Gutenberg Restrict Block

Wrap any content block with allow/deny logic.

Each method works independently.

4. Per-Post Restrictions (Sidebar Metabox)

Available in all post types (pages, posts, custom post types).

How to use

  1. Edit any post/page

  2. Locate the Role/IP Restrict box in the right sidebar

  3. Configure the following settings:

Options Explained

• Mode

  • Allow-list – Only selected roles/IPs/logged-in users may view

  • Deny-list – Selected roles/users are blocked

• Roles
Tick the WordPress roles allowed/denied.

• All logged-in users
Enable if you want the rule to apply to any logged-in user regardless of role.

Examples:

  • Allow + All logged-in = private content for users

  • Deny + All logged-in = only guests may view (useful for promotions)

• Denied message
Message shown if access is denied (when no redirect is defined).

• Redirect URL (optional)
Visitors are redirected instead of seeing an error.
Supports external URLs.

5. Global Gate (Settings → Role/IP Restrict)

Used to enforce site-wide access control.

Enable Global Gate

Go to:
Settings → Role/IP Restrict → Global Gate tab

Configuration Options

• Enable global gate
Activates the site-wide restriction.

• Mode

  • Allow-list

  • Deny-list

• Roles (CSV)
Example:

subscriber, customer, editor

• IPs (CSV)
Supports:

  • Exact IPs

  • Wildcards (192.168.*.*)

  • CIDR (10.0.0.0/8)

• Pools (CSV)
Enter names of IP pools you created (see next section).

• Include current IP
Adds your own IP to the rule — useful when locking a site during setup.

• Bypass admins
Administrators always get access.

• All logged-in users
Same as in per-post rules.

• Redirect URL
URL where blocked users should be sent.

• Denied message
Used if redirect is empty.

• Exclude paths
One path per line, e.g.:

/wp-login.php
/public/

Paths starting with these strings bypass the global rule.

6. IP Pools

Go to:
Settings → Role/IP Restrict → IP Pools tab

You can create named IP groups such as:

  • “Office network”

  • “VPN range”

  • “Finland HQ”

Supported IP formats:

  • 123.123.123.123

  • 123.123.*.*

  • 10.0.0.0/16

These can then be referenced by name in the Global Gate (CSV of pool names).

7. Restricting Content in Gutenberg (Block Editor)

The plugin includes a block:

🧩 Visibility Restrict (Wrapper)

You can find it under Design category.

How to use

  1. Add the Visibility Restrict (Wrapper) block

  2. Insert any blocks inside it

  3. Configure visibility rules in the right sidebar

Block Options

  • Mode: Allow / Deny

  • Roles

  • All logged-in users

  • Denied message

  • (Pro-ready) IPs & Pools

Frontend behavior

Blocked content is not rendered.
It is not visible in the source code.

8. Troubleshooting

Visitors get redirected to wp-login instead of custom URL

Ensure:

  • Redirect URL is valid

  • Redirect field is filled in metabox or global gate

My IP does not match wildcard

Use:

  • 192.168.*.*
    NOT

  • 192.168.0.*.*

Content hidden inside block

Check the Allow/Deny mode — the most common mistake.

9. Support & Updates

Your one-time license includes updates while the plugin remains in active development.

If you need help, contact:
support@lieska.net

Related products