By default, the WordPress admin bar appears in both the frontend (your site’s public view) and the backend (admin dashboard).
With Hide Admin Bar Pro, you can control visibility separately for each — on a per-role basis. This is ideal for improving user experience while maintaining backend access when needed.
When to Use Frontend/Backend Split #
- 🧑💼 Hide the toolbar on the frontend for Subscribers, but show it on the backend
- 🛍️ WooCommerce store: allow staff to access
/wp-admin
, but keep storefront clean - 🎓 LMS: let students see dashboard tools, but remove distractions on course pages
How to Use the Frontend vs Backend Visibility Feature #
1. Make Sure You’re Using Pro #
Not installed yet? See installation guide
2. Open Plugin Settings #
Go to:
Settings → Hide Admin Bar Settings
3. Locate the Pro Visibility Settings #
You’ll see two new fields:
- ✅ Hide Admin Bar on Frontend (By Role)
- ✅ Hide Admin Bar on Backend (By Role)
Each field lets you select one or more user roles.
4. Select Roles for Each Context #
Example: #
- Frontend:
Subscriber
,Customer
- Backend: (leave empty to allow access for all)
You can mix and match based on your workflow.

5. Save Changes #
Click Save Changes at the bottom of the page.
Changes apply instantly — users will see/hide the toolbar based on current context (is_admin()
vs frontend view).
How It Works (Logic Overview) #
- The plugin detects whether the request is in the backend (
is_admin()
). - It then checks the role-based list for that context.
- If the user’s role matches and the rule applies, the admin bar is hidden accordingly.
🔧 You can hook into
hab_pro_should_hide_admin_bar
if you want to apply custom conditions.
Frequently Asked Questions #
FAQs (Frontend+Backend) #
- Does this work with custom roles?
Yes — any role registered in WordPress will be listed automatically.
- What if I select the same role in both lists?
The admin bar will be hidden on both frontend and backend for that role.
- Can I hide the admin bar only on certain admin pages (like profile)?
Not yet — but you can do that via URL/page targeting