Can you hide the WordPress default Administrative Menus so that a website owner doesn’t get confused with all of the options? This member wants to know if it is possible to hide those menus. In this video I explain the options available and suggest a solution that gives the site owner maximum flexibility while de-cluttering the dashboard for day to day work.
Select the link below to watch a high definition version of this video
[S3VIDEO file=’public/liveanswers/LA12-06-10a-can-you-hide-administrative-menus.mp4′ bgimage=’https://www.byobwebsite.com/wp-content/uploads/2012/09/LA12-06-10a-can-you-hide-administrative-menus.jpg’ displaymode=’overlay’]
Brian asks, “Can the dashboard that the client sees be limited to a very small subset simplified?” Well, there’s a couple of ways to approach that, Brian. One of them is to give your clients a couple of different accounts. You know, you can give them an administrator account and tell them that’s the scary one. That is the one that gives them full and complete access to everything. And then you can give them an author account and the author account can be the one where they make new posts or pages or add categories. And that does actually remove all of the administrative menus and you can test what that looks like if you create an author user and then log in as an author user.
You know there’s this standard user in WordPress and we’ll just open up somebody here, just a second. And we look at their, you know, there’s a standard user, subscriber, administrator, editor, author, and contributor. If you make them an author or an editor, maybe an editor is the right one. If you make them an editor, they don’t have all the administrative privileges but they can still add and edit posts and pages and categories and tags and that sort of thing, without seeing all the rest of it. So that’s sort of the easy way to accomplish what you’re asking. You just give them both but you tell them, you know, do most of your work generally in the editor role and then you won’t get confused by all this.
The more Draconian solution to that is to remove administrator menus in your custom functions.php file and you can in fact, programmatically remove these administrative functions…these administrative menus here for example, you can remove any one of these tags from this menu system by using a command in your custom functions.php file. The problem with that is the only way for them to get back to that is to switch themes because your custom functions.php obviously only functions inside of Thesis. So they have switch themes in order to get back to real control, well they have to change your programming.
I think it’s probably kinder to them to just tell them, “Well you can do anything you want with your site including kill it with that administrator tag… with that administrator log in. But if you want a nice, safe log in that gives you access to all the stuff that you ordinarily want to do, then use your editor log in and by using your editor log in, you can’t inadvertently screw anything up.” That’s probably how I would approach it. You know, that’s how Unix approaches security. You have one user that has absolute God-like control over the server and then you have other users that have different controls. And the person who has the root user status will still generally not sign in as the root user, they’ll still generally sign in as a regular user because they don’t really need that absolute control.