Navigation, dashboards, widgets and information pages
Navigation and sections
Edit a role's Sidebar & View, or open a View under Shared Views. Native menu editing supports labels, Shown/Hidden switches, icons, search, expandable submenus, custom shortcuts and separators. Drag handles, move buttons and Alt+Up/Down provide ordering controls. Reordering retains the original submenu parent. Renaming Posts changes its menu label, not its content type, frontend URL, REST identity or native screen title.
Enable Section sidebars to copy visible menus, shortcuts, guides and dashboard destinations into Main. The native menu settings remain stored and return when section navigation is disabled. Sections contain native destinations, information pages, links, separators and child sections; each has an introduction, quick-access cards, widget order and one/two-column dashboard. Use Options → Move to sidebar to move items or whole child branches. Deleting a section in the editor moves its items and children to its parent; widgets stay in the library.
Free permits Main and two direct children. Pro permits fifty total sections and eight levels below Main. The one-step Group Posts & Pages into Content arrangement can introduce deeper sections, so its resulting structure must satisfy the current plan. Cycles, missing references, duplicate parents and over-depth structures are rejected.
Section context travels in wpa_section in the URL, allowing different tabs to use different sections. Normal links, forms and native save redirects retain it; direct links can infer context from the destination. The fullscreen block editor keeps its own shell and returns to contextual navigation on exit. Inactive-plugin destinations are omitted. Plugins that replace the admin shell or bypass ordinary links/forms may need an adapter. Section overview access uses the Client home permission; section links never grant capabilities.
Dashboard and widget library
Choose native WordPress dashboard or a dedicated client home, with one/two columns and half/full-width widgets. Managers control the custom client-home layout. Native WordPress widgets retain normal per-user position/collapse preferences. The same library widget can appear in multiple permitted Views and section dashboards without consuming another slot.
| Widget | Purpose / boundary |
|---|---|
| Welcome | Personalised greeting and rich-text introduction |
| Information | Rich-text guidance inside a dashboard card |
| Quick actions | Shortcuts to permitted admin destinations or validated links |
| Recent content | Configured post types and 1–20 displayed items, filtered by what the viewer can edit |
| Content overview | Status counts from the recent-content sample; not complete site totals |
| Checklist | Named items with persistent completion per user or shared across authorised viewers |
| Help and support | Rich-text support/contact guidance; does not itself implement a helpdesk service |
All seven types are Free. The Free library limit is three unique entries including drafts and archives; Pro allows up to 200. Rich text uses WordPress's editor and media picker, with a restricted HTML allowlist. Scripts, arbitrary embeds and executable content are not accepted. Recent/overview widgets examine up to the latest 100 records before edit-permission filtering, so they are not analytics or full-site reports. Checklists are disabled in preview.
Information pages
Information pages are private PanelKind admin guides with a title, menu label, icon, rich text and draft/published/archived status. Place them at top level, under Help or inside sections, and assign permitted Views and audiences. They are stored in private configuration snapshots and rendered by authorised admin callbacks, without a public post type, feed, sitemap or public content REST route.
Free allows one library page; Pro allows 200. Both editions support all signed-in users, selected roles or owners as audiences; Pro adds individual-user targeting. Audience eligibility does not grant native access or override resource policy, and a widget/page must also be placed appropriately to appear. Owners have protected audience access.
Ordinary linked images and downloads can still have public WordPress upload URLs. A private guide does not implement protected file delivery. Archive hides content while retaining it; remove dependent placements/references where validation requires this. Delete unused entries to release Free capacity.