Skip to content

How-to Guides

Technical References

Restricting Site Access /

Restricting access via Authentication

There are many different ways to restrict access to your applications and environments on VIP Go. Here, we review the various techniques available.

Note

The IP Allow List and Basic Authentication access restriction methods cannot both be active at the same time. If you attempt to activate them both, Basic Authentication will take precedence.

Restricting via Authentication (Full Site)

When and how to use

If you want to restrict access to authenticated users only, you can use one of the many WordPress plugins that support this functionality like Force Login or Registered Users Only. If your organization has a Single Sign On (SSO) system, you can simplify the login process for your team by integrating it into the login flow.

What is restricted

Once enabled, logged out users would be required to login and verify permissions before being able to access the site.

Please note that the restrictions will only apply to content generated by WordPress. Media and static assets will continue to be publicly accessible.

Content will also continue to be syndicated via Jetpack’s content distribution tools. To change this behavior, please see Controlling Content Distribution via Jetpack.

Restricting via Authentication (Temporary)

When and how to use

If you want to temporarily restrict access to a site (e.g. when the site is under development or for pre-launch configuration), you can use the Maintenance Mode plugin.

What is restricted

After installing and configuring the plugin, only users with Author-level access and above can access the site.

Please note that the restrictions will only apply to content generated by WordPress. Media and static assets will continue to be publicly accessible.

Content will also continue to be syndicated via Jetpack’s content distribution tools. To change this behavior, please see Controlling Content Distribution via Jetpack.

Last updated: November 24, 2020