In this guide: A complete WordPress dashboard tour: every admin menu explained — posts, pages, media, appearance, plugins, users, and the settings you must review.
The first time you log in to WordPress, the dashboard can feel like a cockpit full of unfamiliar buttons. The good news: the menus become easier to navigate when you connect each screen to a specific task. The exact dashboard depends on your role, version, theme and installed extensions.
After logging in at yoursite.com/wp-admin, you land on Dashboard → Home. It shows:
Click Screen Options (top right) to hide boxes you don’t need. Dashboard → Updates shows available updates for WordPress core, themes, plugins, and translations.
The top admin bar (visible when you’re logged in and viewing your site) gives quick links to create content, edit the current page, and visit the dashboard.
Posts are time-based content — blog articles, news, tutorials. They appear in your blog feed, have categories and tags, and are included in RSS feeds.
Pages are static content — Home, About, Contact, Services, Privacy Policy. They don’t use categories or appear in the blog feed, but they can have parent-child relationships (for example, /services/web-design/).
Media is your library of images, videos, PDFs, and other files. Tip: rename image files descriptively before uploading and provide appropriate alternative text for informative images and suitable treatment for decorative images. See how to optimize images for the web.
Comments lets you approve, reply to, mark as spam, or delete comments.
Appearance controls how your site looks. Options depend on whether you use a block theme or classic theme:
Plugins is where you add features:
Keep plugins lean — evaluate actual requirements before using 15 essential WordPress plugins as an automatic installation list.
Users manages everyone who can log in:
Assign the lowest role needed: Administrators have full control; Editors manage all content; Authors publish their own posts; Contributors write but can’t publish; Subscribers can only manage their profile. Learn more in WordPress User Roles and Permissions Explained.
Tools includes import/export, Site Health, and privacy tools for handling personal data requests.
The Settings menu contains options that affect your whole site. Understand the purpose of these settings and review relevant changes through an authorized process:
https://), admin email, time zone, date format, and site language.Plugins often add their own settings pages here or as new menu items in the sidebar.
Why do I see different menus than someone else?
Menus depend on your user role, your theme type (block vs classic), and installed plugins.
Can I hide menus for clients?
Choose the capabilities needed for the actual tasks. Hiding a menu alone does not remove the underlying permission.
Further reading: official WordPress documentation
Before making a change, confirm which website and environment the dashboard controls. A staging copy can look almost identical to production. Check the visible site identity, public address and intended task. Do not rely on the browser tab’s position or a familiar logo alone. The same person can have several installations open with different accounts and responsibilities.
Use the business’s authorized account and keep credentials out of articles, screenshots and support messages. If the displayed account has unexpected access or the website is unfamiliar, resolve that uncertainty before editing. A dashboard is an operating interface, so choosing the correct target is part of the task rather than an optional precaution.
A missing menu does not automatically mean the website is broken. User capabilities, the installed theme, network configuration and plugins can change the visible interface. WordPress’s administration screen guide describes the general structure. Compare it with the actual installation instead of assuming every screenshot from a tutorial applies unchanged.
When a colleague sees an option you do not, record the task and ask the responsible owner to review the intended permission. Do not request full administrator access merely to match a tutorial. The required capability should follow the job, and hiding an option cosmetically is different from restricting the underlying action.
The dashboard’s content lists can contain published, scheduled, draft and private items. Confirm the selected filter before interpreting a total. Search the appropriate content type and review the title, status and date. A scheduled article should not be described as public just because it appears in the administration list.
Bulk actions can affect many records at once. Check the exact selected items and action before submitting. For a routine correction, opening the relevant item is often clearer than selecting a broad collection. Keep existing publication schedules and public addresses unless the actual assignment requires changing them.
A preview can show unsaved changes. An autosave can preserve work without establishing that the public page was updated. After an authorized edit, confirm the saved status and inspect the public result appropriate to the task. Record any difference between the editor and the public page instead of assuming a button press completed the whole workflow.
The dashboard may also expose newsletter or social integration controls. Review the actual publish action and notification options before creating a new public post. Updating content does not authorize sending an unrelated subscriber campaign. The launch checklist explains how to keep preparation, publication and distribution evidence distinct.
An image used on one page can also appear in another article, a reusable section or a social preview. Review its usage before deleting or replacing it. Changing an attachment’s description does not necessarily update every existing image instance in the same way, so inspect the relevant public content after a media-related correction.
Use the dashboard media library to locate the actual asset and verify rights, dimensions and meaning. Avoid adding irrelevant pictures to satisfy an editor score. A useful diagram should explain the subject accurately and include dimensions and appropriate alternative text. Keep illustrative images distinct from screenshots or measurements that claim to document a real test.
Editing a page’s text differs from changing the template, navigation or global styles that can affect many pages. Identify which screen owns the element before modifying it. The Site Editor depends on the theme and configuration, while a builder can add another design workflow. Do not assume the dashboard’s Appearance menu represents the same controls on every installation.
Our Elementor and Gutenberg comparison helps clarify editing ownership. For a small content correction, stay in the appropriate content scope. A global color or template change needs a broader review of representative pages and responsive behavior because its effects extend beyond the item currently visible.
An update badge indicates available work, not a complete deployment plan. Identify the component, supported version and relevant dependencies before applying an update. A shop, membership website or custom integration may need representative testing and a recovery plan. The dashboard can start an update but cannot decide whether every business journey remains correct afterward.
Use our WordPress update workflow and keep a verified backup. Restoring an old database can remove newer orders or enquiries, so recovery requirements depend on the site’s activity. Do not promise that one automatic update setting eliminates the need for maintenance ownership.
The dashboard’s Site Health information can identify conditions that deserve review. It is not a comprehensive security certificate or a guarantee of performance. WordPress’s Site Health screen documentation explains its status and information sections. Read the particular message and the actual environment before applying a generic fix.
Some recommendations depend on the host or architecture. Record the issue and pass it to the responsible operator when the change is outside your task. Diagnostic exports can contain technical details about the website; share only the information needed with the intended support recipient rather than posting the full record publicly.
A content export is not automatically a complete restorable copy of the website. Files, database content, configuration and external services can have different recovery requirements. The dashboard’s export tool serves a particular content-transfer purpose. Confirm the backup system’s actual scope before relying on it during a migration or incident.
Our automatic backup guide explains why a successful job needs a verified recovery process. Keep the recovery owner and storage destination documented. Do not store sensitive backup archives in a publicly accessible media location simply because uploading through the dashboard is convenient.
Record the screens needed for routine tasks, who can perform them and what a successful result looks like. Include the public verification step and any relevant notification controls. A short handover organized by actual tasks is easier to use than a screenshot of every dashboard menu without explanation.
Use the WordPress roles guide and the official roles and capabilities documentation to review responsibilities. A user account’s visible role name is a starting point; custom capabilities and network arrangements can alter the actual access model.
Imagine an editor correcting a service page and adding a link to a published guide. The editor first confirms the production site and the exact page. It reviews the existing public address, changes the relevant paragraph and previews the result. After the authorized update, it confirms the success notice and opens the public page to inspect the changed text and destination.
If the public page still shows older content, the editor records the symptom and checks the supported publishing workflow with the maintainer. It does not repeatedly republish unrelated items or disable security features. A cache layer, wrong page target or unsaved change can produce similar appearances, so the next action should follow the evidence.
This example is a method, not a claim that a particular dashboard task has been performed on the reader’s site. The same pattern works for many routine edits: identify the target, make the scoped change, confirm the saved state and inspect the relevant result. The details depend on the actual editor and installed integrations.
Promotional recommendation: KAWEDMA WordPress development and website services may be relevant for a scoped setup, troubleshooting or maintenance project. Confirm the task, account ownership, deliverables and ongoing responsibilities before ordering. This recommendation does not mean every service includes administrator training or every possible plugin integration.
If the actual need includes a different managed WordPress environment, evaluate that separately. Affiliate disclosure: Hostreta may earn a commission from purchases through this hosting.com WordPress hosting referral. Verify current features and terms. A hosting subscription does not automatically teach a user every dashboard task or replace a site-specific handover.
If a screen unexpectedly changes the target website, asks for unfamiliar permissions or offers an action outside the intended task, pause that action and confirm the context. If a routine menu is missing, inspect the role and configuration rather than assuming a broken installation. If a save appears to fail, verify the stored result before repeating a potentially consequential action.
Keep the exact page, task and observed message in a concise record. A screenshot can help when it excludes private data and shows the relevant state. Clear evidence gives the maintainer a useful starting point and avoids broad changes that obscure the original problem.
Use a short routine based on the website’s activity rather than clicking every menu. Review the intended content queue, publication dates and unresolved maintenance messages. Check whether a scheduled item became public as expected before reporting it as published. Keep a list of items that need another person’s decision so they do not disappear among dashboard notifications.
For a publishing team, compare the stored article status with the editorial plan. Confirm that the correct version, author and related links are present. For a business website, include the important enquiry and purchase routes in the broader operating review. The dashboard is one source of evidence; the public customer journey provides another.
When a plugin adds a new dashboard panel, identify its purpose before using its controls. A summary can be informational while an adjacent button starts a paid service, changes a configuration or sends content to another system. Read the actual action and keep it within the site’s approved workflow. Familiar placement in WordPress does not make every third-party action equivalent.
Review the team’s handover after a meaningful configuration change. If the site switches from a classic theme to a block theme, for example, the location of design work may change. Update the task instructions and test the editor’s ordinary actions. Avoid maintaining an obsolete walkthrough that tells a new user to change a global template for a simple content correction.
Close the weekly dashboard review with verified work, named unresolved issues and the next necessary action. Keep the evidence proportionate and free of secrets. A concise record helps the business distinguish a completed edit from an intention, an available update from an installed one, and a draft from a public page.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.