Skip to content
Front User Submit
Menu

How to Hide WP Admin From Users on WordPress

By Aleksan Aharonyan ·

Hiding wp-admin from users means sending anyone who is not an administrator away from the WordPress dashboard and giving them a front-end page for the work they actually do. It is a usability change, not a security one, because WordPress roles already decide what each person can read, write and delete. What the redirect fixes is the confusion of dropping a member into an admin full of menus that lead nowhere.

Key takeaways

  • WordPress roles decide what a user can do and hiding wp-admin only decides where they land, so treat the redirect as a usability fix and set capabilities separately.
  • A Subscriber has almost nothing to do in wp-admin beyond their own profile, so hiding it costs them nothing as long as a front-end dashboard replaces it.
  • The admin bar is a separate job: blocking /wp-admin/ does not remove the toolbar logged-in users see on the front end, which still links back to the dashboard.
  • Test the redirect with an account that has the real role, and leave administrators, AJAX requests and the login flow unblocked.

What can a subscriber actually do in wp-admin?

A Subscriber can open their own profile screen and little else. The content work starts at the Contributor role, which can write and save drafts but not publish them, and at Author, which can publish its own posts.

WordPress checks capabilities on every admin screen and on every REST request, so a menu a role cannot use is refused anyway. The admin is cluttered for a Subscriber, not dangerous. That distinction shapes how you fix it.

The default roles, roughly:

  • Subscriber: their own profile.
  • Contributor: their own drafts, and a way to submit them for review.
  • Author: their own posts, including published ones, plus media uploads.
  • Editor: everything about posts and pages, including other people’s.

Plugins and themes add screens on top of that, and some add menu items to roles that cannot do much with them. Check what your own site adds before deciding the admin is useless to a role.

Why hide wp-admin instead of just changing roles?

Changing roles changes permissions, and hiding wp-admin changes the address people start from. You usually want both, and neither does the other’s job.

If your members only need to write and manage their own posts, making them Contributors and letting them use wp-admin is a legitimate setup. A site with two or three contributors who already know WordPress does not need a front-end layer at all. The case for hiding wp-admin starts when the dashboard is mostly noise: menus for themes, plugins and tools the person cannot use, plugin notices, an empty profile screen, and no obvious way back to the site.

The case against treating it as security is stronger. A logged-in user who types an admin URL still reaches whatever their role allows, and the AJAX endpoints that front-end features use stay open by design. If your real worry is somebody publishing something they should not, the fix is a capability change plus a review step: WordPress already has the Pending status, and a post can sit there until an editor looks at it.

Which approach fits: a redirect, a setting or a front-end dashboard?

There are three moving parts here, and most sites need all three: a redirect that keeps non-administrators out of wp-admin, a role that gives them only the capabilities they need, and a front-end page where they can work.

The redirect. This is a small piece of code in a site-specific plugin or a child theme, or a switch in an admin-hiding plugin. It runs at the start of each admin request, checks the current user, and sends anyone without the right capability to a URL you choose. Leave administrators out of the rule, and let AJAX requests pass through untouched.

The role. New accounts get the site’s default role, which you set in WordPress. Pick the lowest role that still lets the person finish the job, and remember that changing the default does not change accounts that already exist.

The destination. Users need somewhere to go after the redirect. Front User Submit, a free plugin for frontend post submission and guest posting forms, provides one with the [fe_fs_user_admin] shortcode: a front-end page with Publish, Pending and Draft tabs and edit and delete icons for each post. The user dashboard documentation lists what each tab shows and which settings control it.

Without the third part, the redirect just makes people ask you for help.

How do you keep the admin bar off the front end?

The admin bar is a separate setting from the wp-admin redirect. A logged-in user who is blocked from /wp-admin/ still sees the toolbar across the top of your site, and that toolbar links straight back to the dashboard.

There are three places to deal with it:

  • Per user, with the “Show Toolbar when viewing site” checkbox in each profile. Fine for a handful of accounts and tedious beyond that.
  • With a filter in code that returns false for anyone who is not an administrator, so the toolbar disappears for everyone else.
  • With a plugin setting. Front User Submit’s global settings include a switch for the WordPress admin bar that hides it from users without any code, and the global settings documentation describes the tabs on that page.

Whichever route you take, leave the toolbar visible for administrators. It is the quickest way into the dashboard, the customizer and the new-post screen, and losing it on a site you manage daily gets old fast.

Then give users a visible link to whatever replaced wp-admin: an item in your main menu, a footer link, or a link on the page members land on after login. The admin bar was doing that job by accident.

What should users be able to do once wp-admin is closed to them?

Once wp-admin is closed, a user still needs four things: a way to log in, a way to register if you allow registration, a list of their own posts with clear statuses, and a way to edit or delete those posts without emailing you.

Login and registration are the first gap. The WordPress login screen still works, but it lives in the area you are steering people away from. Front User Submit adds [fus_form_login] and [fus_form_register] shortcodes for front-end forms with a redirect after login, and the user dashboard and login documentation covers where to place them.

One thing to know about registration: new accounts get the site’s default role, and since version 5.2.5 the form emails a link to set a password, like the WordPress registration page. If that email does not arrive, people can set a password with the WordPress “Lost your password?” page, so link it under the login form.

The post list matters more than it sounds. A user who submits a post needs to see whether it is Publish, Pending or Draft, otherwise they submit it again. Editing should reuse the same form they submitted with, so the fields and the expectations stay the same.

Deleting is where roles reappear. What a delete icon does depends on the user’s WordPress role: by default Subscribers cannot delete posts, Contributors can delete their own unpublished posts, and Authors can delete their own posts. If the icon is missing, the role is the reason, not the dashboard.

Which mistakes lock you or your users out?

The two ways this goes wrong are locking yourself out and breaking something that quietly relied on wp-admin.

  • Redirecting administrators. Check the capability, not the role name, and test in a private window while signed in as an administrator. If your rule catches you, getting back in means removing the code over FTP or your host’s file manager.
  • Blocking AJAX. Front-end forms, dashboards and plenty of plugins send requests to the admin AJAX endpoints. If the redirect catches those, uploads and submissions fail with no clear error. Exclude AJAX requests from the rule.
  • Redirect loops. Sending users to a page that itself requires a capability they lack bounces them around until the browser gives up. Send them to a public page or to the dashboard you built for them.
  • Editing the theme directly. A theme update wipes the snippet. Use a child theme or a small site-specific plugin.
  • Forgetting password resets. A set-password email that never arrives plus no visible reset link equals locked-out members and support requests.
  • Treating hidden as secure. Capabilities, Pending review and a moderation habit are what protect the site; a redirect only changes where people start.

FAQ

Is hiding wp-admin the same as securing the site?

No. WordPress decides what a user can do through the capabilities attached to their role, and it enforces those on every screen and every REST request, whether or not the user can see the menu. Hiding wp-admin only changes where they land. Keep roles tight, keep new posts in Pending when you do not know the author, and review what gets published.

What do users see instead of wp-admin?

They see whatever you build for them. A front-end dashboard is the usual answer: a page listing their posts by status with edit and delete actions, plus login and registration forms so they never need the WordPress login screen. Front User Submit’s [fe_fs_user_admin] page does this and is created when you activate the plugin, so there is something to point the redirect at from day one.

What happens when a member forgets their password?

They use the WordPress “Lost your password?” page, which emails them a reset link. Many front-end setups have no reset form of their own, so link that page from your login form and your dashboard. If your site cannot send mail reliably, that page will not help, so test it with a real account before you rely on it.