mortenf

<p>This plugin adds optional per-page user name and password protection, implemented using standard HTTP protocol authorization headers, thus triggering the standard user/password dialog of the browser, and making it possible to make the browser store the credentials.</p>
<p>Subpages of a protected page are protected with the same user name and password as their parent.</p>
<p>Protected pages and their subpages do not show up in menus, search results and page lists.</p>
<h4>Usage</h4>
<ol>
<li>When editing a page, locate the section titled “Page Protection” (probably located near the bottom of the right sidebar).</li>
<li>Check the box “Protect page and subpages”, and provide a user name and password combination.</li>
<li>Optionally, check the box “Make page and subpages searchable”, if you want the page and its subpages turn up in search results, but only with their title, not their content.</li>
<li>Save your page.</li>
</ol>
<h3>License</h3>
<p>Copyright (c) 2009 Morten Høybye Frederiksen <a href="mailto:morten@wasab.dk" rel="nofollow ugc">morten@wasab.dk</a></p>
<p>Permission to use, copy, modify, and distribute this software for any<br />
purpose with or without fee is hereby granted, provided that the above<br />
copyright notice and this permission notice appear in all copies.</p>
<p>THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES<br />
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF<br />
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR<br />
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES<br />
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN<br />
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF<br />
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</p>


Page Protection

Protect pages and their subpages with user name/password, and keep protected pages from showing up in menus, search results and page lists.

WPRuby

Waseem Senjer

<p>Give a temporary limited admin. access to themes designers, plugins developers and support agents.</p>
<p>The plugin is simple and clean, it helps the administrator to create a user with a temporary access and choose which pages in your admin area which you don’t want the user to access. send the details to the user and when he finished his task, you can easily deactivate the account and activate it later.</p>
<ul>
<li><a href="https://wpruby.com/plugin/controlled-admin-access-pro?utm_source=lite&utm_medium=readme&utm_campaign=freetopro" title="Upgrade to Controlled Admin Access Pro" rel="nofollow ugc">Upgrade to Pro Now</a></li>
<li><a href="https://wpruby.com/knowledgebase_category/controlled-admin-access-pro/" title="Documentation " rel="nofollow ugc">Documentation</a></li>
</ul>
<h3>Features</h3>
<h3>Menu Filter</h3>
<p>The plugin will allow you to select admin menu items that you want to restrict for the created admin. Not only the plugin will hide the menu item from the admin but it also will block the page if they access it in some other way.</p>
<h3>Expiration Time</h3>
<p>You may don’t want to give access indefinitely, the plugin allows you to set an expiration time for the restricted admin account. After the account expires, the account will no longer be able to login into the admin dashboard. Moreover, you can always extend the expiry time or change it.</p>
<h3>Hide Admin Bar</h3>
<p>WordPress offers an admin bar to provide quick access to some pages or to perform some actions. Using the plugin, you can hide the admin bar links at the top of the page will be hidden in both the frontend and admin areas.</p>
<h3>Disable Access</h3>
<p>You can always disable the restricted admin account at any time. For example, if you gave a developer access to fix a bug or install a theme, when they finish the task you can disable their account. This will block login in using the account but it will retain the account’s information in case you wanted to give them access in the future.</p>
<h3>Pro Features</h3>
<h3>Plugins Internal Pages</h3>
<p>Take more control and restrict access to plugins’ internal pages. For example, you would like to give access to the WooCommerce Settings page, but you do not want the account to see the Payments Gateways tab. Currently, the plugin supports WooCommerce, Easy Digital Downloads and BuddyPress. In the future, we will add support for more plugins.</p>
<h3>No Password Login</h3>
<p>Add some convenience when sending access to the user, you can generate a secure login URL for the user, and the user will use the link to login into the dashboard without the need for a password. You can also disable login by a password for restricted admins, this will restrict the admin from login in using a password or sending a reset password email.</p>
<h3>Activity Log</h3>
<p>Keep track of what restricted admins have done while logged in, the plugin will log more than 20 actions such as activating/deactivating/deleting a plugin, switching a theme, deleting a theme, exporting data, publishing/deleting a post and uploading a file.</p>
<h3>Remote Logout</h3>
<p>At any given time, you can force logging out any restricted admin if you no longer need them logged in the admin dashboard. This action will log them out on all logged-in devices and locations.</p>


Controlled Admin Access

Controlled Admin Access is an excellent plugin. Just keep in mind that the access you need to provide is still controlled by WP user controls.
Ex: CF7 forms need admin access by WP. If the new user is not given admin access at WP level, the Controlled Admin Access can not provide the access. 
Have tried with different WP and CAS levels and found this behaviour. Nevertheless, the controls are very good and useful. Flip side "could be" a WP admin access has to be given and CAS filters access.

Excellent plugin

Give a temporarily limited admin access to themes designers, plugins developers and support agents.

Page Protection vs Controlled Admin Access