snapaura

SnapAura Menu Manager gives you granular control over when and where your menu items appear. Perfect for creating dynamic navigation that adapts to your visitors’ context.
Features:
<ul>
<li>Login State Control – Show menu items only to logged-in or logged-out users</li>
<li>User Role Visibility – Show menu items only to specific user roles (Administrator, Editor, Author, Contributor, Subscriber)</li>
<li>Device-Based Hiding – Hide items on mobile, tablet, or desktop devices</li>
<li>Current Page Hiding – Automatically hide menu items when viewing that page</li>
<li>Works with Any Theme – Compatible with all WordPress themes</li>
<li>No Configuration Required – Simple checkboxes in the menu editor</li>
</ul>
Use Cases:
<ul>
<li>Show “Login” only to logged-out users and “Dashboard” only to logged-in users</li>
<li>Show “Edit Posts” only to Editors and Administrators</li>
<li>Show “Submit Article” only to Authors and Contributors</li>
<li>Hide contact links on mobile to save space</li>
<li>Create different navigation experiences for different devices</li>
<li>Remove redundant navigation when already on a page</li>
</ul>
How It Works:
<ol>
<li>Go to Appearance > Menus</li>
<li>Expand any menu item</li>
<li>Check the visibility options you want</li>
<li>Save your menu</li>
</ol>
No complicated settings or configuration files. Just simple checkboxes that do exactly what they say.

SnapAura Menu Manager

Control menu item visibility based on login status, user roles, device type, and current page.

Kevin Behrens

thomstark

Show or hide any portion of post content based on usernames, user roles, capabilities, custom groups, or logged-in status. Construct shortcodes manually or using a point and click UI.
<h4>Mini Update Log</h4>
<ul>
<li>v1.8.2 compat with WordPress 3.9</li>
<li>
v1.8.1 fixed conflict with the Tabify Edit Screen plugin
</li>
<li>
v1.8 added new shortcode handlers for nesting eyesonly shortcodes. also added body classes for logged-in user roles and logged-in usernames.
</li>
<li>
v1.7.1 fixed bug with TinyMCE button where TinyMCE panel is used outside post/page editor.
</li>
<li>
v1.7 added multisite support for username multiselect; fixed bug with role/level dropdown in non-Mozilla browsers.
</li>
<li>
Lots of new features in v1.6, including smooth integration with Role Scoper and Press Permit, thanks to their author Kevin Behrens, who has also now joined the Eyes Only team. Two makes a team, right?
</li>
<li>
As of v1.5, has compatibility with BuddyPress and BBPress forums in conjunction with the bbPress2 shortcode whitelist plugin by Anton Channing.
</li>
<li>
As of v1.4, includes TinyMCE Shortcode Button with Shortcode Generator Modal, with options to restrict access to the Shortcode Button, and to determine its position on the TinyMCE panel.
</li>
<li>
As of v1.3, includes Options page, with options to restrict access to the Meta Box, and to prevent content being hidden from Administrators.
</li>
<li>
As of v1.2, includes Shortcode Generator Meta Box
</li>
<li>
<a href="https://wordpress.org/plugins/eyes-only-user-access-shortcode/changelog/" title="Right-Click to Open in New Window">See full changelog</a>
</li>
</ul>
<h4>The Shortcode</h4>
[eyesonly] [/eyesonly]
or
[eyesonlier] [/eyesonlier]
or
[eyesonliest] [/eyesonliest]
<ul>
<li>
Required attributes: either logged=”in|out” or level=”anyrole, any_capability” or username=”anyusername” or all three
</li>
<li>
Newly integrated attributes: rs_group=”any_Role_Scoper_group(s)” or pp_group=”any_Permit_Press_group(s)”
</li>
<li>
Optional attribute: hide=”yes”
</li>
</ul>
All shortcodes must include at least one of the three required attributes. In some cases, it makes sense to use all of them together.
<ul>
<li>
The ‘logged’ attribute takes one of two values: ‘in’ or ‘out’
</li>
<li>
The ‘level’ attribute takes any user role (including custom roles) or any capability (including custom capabilities). It can take multiple roles and/or capabilities, separated either by spaces or commas.
</li>
<li>
The ‘username’ attribute takes any userlogin (username), or multiple, separated either by spaces or commas.
</li>
<li>
The ‘rs_group’ and ‘pp_group’ attributes can take comma or space-separated lists just like the ‘level’ and ‘username’ attributes. If you have the latest versions of either Role Scoper or Press Permit activated, you’ll get an extra menu in your shortcode generators to filter your content by those custom user groups. This attribute can also be used in combination with any of the others to fine tune your filtering.
</li>
<li>
The ‘hide’ attribute: By default, the shortcode will show the content only to the users specified by the ‘username’, ‘level’ or ‘logged’ attributes. Adding the ‘hide’ attribute will reverse that, and hide the content from the specified users. To hide content from the specified users, use hide=yes or hide=true.
</li>
</ul>
Any other shortcode can be used inside this shortcode.
<h4>Examples</h4>
<ul>
<li>
[eyesonly level=”administrator, customrole, moderate_comments”] Any kind of content. [/eyesonly] This will show the content only to users with the ‘administrator’ role, the ‘customrole’ role, and the ‘moderate_comments’ capability.
</li>
<li>
[eyesonly hide=”yes” logged=”out” level=”subscriber customrole”] Any kind of content. [/eyesonly] This will hide the content from all logged out users, and from anyone with the roles ‘subscriber’ or ‘customrole’.
</li>
<li>
[eyesonly username=”joebob, billyjean” level=”administrator”] Your content. [/eyesonly] This will show the content to all administrators and to the specific users ‘joebob’ and ‘billyjean,’ whether they’re administrators or not.
</li>
<li>
[eyesonly logged=”in”] Content for logged-in users. [/eyesonly][eyesonly logged=”out”] Content for logged-out users. [/eyesonly] This will show different content in the same location on the page depending on a user’s logged-in or out status.
</li>
<li>
[eyesonly level=”administrator”] Content. [/eyesonly] This will show the content only to administrators.
</li>
<li>
[eyesonly hide=”yes” level=”administrator custom_capability”] Content. [/eyesonly] This will hide the content only from administrators and from any role that has the ‘custom_capability’.
</li>
</ul>
<h4>Eyes Only Nesting</h4>
<ul>
<li>Eyes Only allows for nested user access shortcodes up to three levels deep. Example:</li>
</ul>
[eyesonly level=”administrator, editor, author”] Restricted content. [eyesonlier level=”administrator, editor”] Restricteder content. [eyesonliest level=”administrator”] Restrictedest content. [/eyesonliest] More restricteder content. [/eyesonlier] More restricted content. [/eyesonly]
<ul>
<li>It doesn’t matter which order you use them in, just so long as you keep your nested levels straight. </li>
</ul>
<h4>Requirements</h4>
<ul>
<li>
PHP 5.2+
</li>
<li>
WordPress 3.3+
</li>
</ul>

Eyes Only: User Access Shortcode

The plugin does the job. The authors should update compatibility :-)



Works

Show or hide any portion of post content based on usernames, user roles, capabilities, custom groups, or logged-in status.

SnapAura Menu Manager vs Eyes Only: User Access Shortcode