Skip to main content

🌏 APAC Community Update: New Admin Menu is coming – and legacy admin is retiring 🚀

  • April 21, 2026
  • 4 replies
  • 133 views
jodie.graves
Docebian

Hi APAC admins!

A new, modern Admin Menu and navigation experience is rolling out as part of the Spring (April 2026) release, with a clear path to fully replacing today’s legacy admin menu later this year.

 

📅 Key dates & retirement timeline

Here’s the official rollout schedule for the New Navigation / New Admin Menu:

  • Sandbox – from 2 March 2026

    • Available in opt‑in preview mode with no impact on existing systems.

  • Spring Release – April 2026 (Production)

    • Available in production as an optional experience; you decide when to turn it on for your admins and users.

  • Summer Release – 22 July 2026 (Global change)

    • New navigation becomes the standard experience for your platform.

    • The legacy admin menu will be fully retired and no longer available.

➡️ What this means for you:

  • You can try and configure the new experience now in sandbox, then opt in on production any time between April and 22 July 2026.

  • After 22 July 2026, everyone will use the new navigation and legacy admin will be removed.

 

⚙️ How to try & activate the New Admin Menu 

Everything you need is available directly from your platform UI:

1️⃣ Preview the new navigation in sandbox

As a Superadmin, you can enable preview mode just for yourself:

  1. Log into your sandbox.

  2. Open the Admin menu and look for the banner announcing the new navigation (for example: “The new navigation is here!” / “Try the new nav”).

  3. Click Try the new navigation or Enter preview mode.

This turns the new navigation on only for your user, so you can safely explore without affecting other admins or learners.

To go back, use the Restore legacy navigation option from the same area or follow the steps in the New navigation interface help article.

2️⃣ Enabling for more admins and users

Once you’re comfortable with the new layout:

  • Use the Feature controls page in the Admin menu to choose who gets the new experience:

    • Just Superadmins

    • Superadmins + Power Users

    • All users (including learners)

You can roll this out gradually (e.g. only Superadmins first, then Power Users, then everyone) any time between April and 22 July 2026.

During the opt‑in period, you can still revert to legacy navigation if needed for additional testing or change management.
 

 

✨ What’s changing in the Admin Menu

The New Admin Menu focuses on speed, clarity, and accessibility:

  • Modern, streamlined layout

    • A cleaner header bar and user menu reduce visual clutter and keep key actions within easy reach.

  • Clear, hierarchical admin menu

    • Admin pages are now organized into a logical hierarchy, so it’s much faster to find user management, content management, reporting, and configuration areas.

  • Better separation of daily tasks vs configuration

    • Frequently used management tasks are surfaced, while more advanced platform configuration lives in a dedicated area, cutting down on clicks for common workflows.

  • Harmony Search in the header

    • You can use Harmony Search in the header to find admin pages, configurations, courses, assets, and more and jump straight to them, including indexed admin menu items.

  • Accessibility‑compliant navigation

    • The new navigation has been designed with accessibility and modern UX standards in mind.

 

💡 Practical tips & tricks

Here are some easy ways to support your teams before legacy admin is retired:

  1. Run “before vs after” sessions in your timezone

    • Open sandbox (new nav) and production (legacy) side‑by‑side in a screenshare. Or have an incognito window and regular window if you do not have a sandbox!

    • Walk through your top 5–10 daily tasks (e.g. create user, enrol learners, run reports) and show where those are in the new menu.

  2. Nominate “Champions”

    • Choose a few local Superadmins/Power Users to test first and collect feedback

  3. Map your custom CSS early

    • If you use custom CSS on the header, breadcrumb, title bar, or menu, test it in sandbox with the new navigation to confirm everything still looks and behaves as expected.

  4. Use Harmony Search as a safety net

    • Show admins how to type the name of a menu item or page into Harmony Search and jump directly there. This is especially helpful right after the switch, when people are still learning the new layout.

  5. Create a simple “Top 10 Paths” cheat sheet

    • Build a quick table or PDF for your company listing:

      • Task → Legacy path → New path .Share this internally so admins can adapt quickly ahead of the July change.

 

🔗 Helpful resources to share with your teams

You can copy‑paste these directly into your own internal comms:

 

Feel free to reuse this post with your local teams to help them get ready for the new Admin Menu and the retirement of the legacy admin experience on 22 July 2026 💙

 

Are you using the new admin menu yet? If so, do you have any helpful tips to share? We would love to hear from you!

    4 replies

    G
    Helper I
    Forum|alt.badge.img
    • gus
    • Helper I
    • April 23, 2026

    Thanks for the heads-up ​@jodie.graves. That’s very helpful.

    Overall I like the clean look, but as always the concern is in the detail. Is there anything which documents all the specific changes? I’ve taken a quick look around and immediately notice that the fonts on our custom pages and buttons are bold, which a) looks terrible and b) some of these no longer fit in the space, and our buttons are no longer rounded. The rounding is done by css, but the elements themselves don’t seem to have changed, so I’m not sure why this would no longer work. I feel like I’m about to have a massive job checking and correcting every page and element on our platform to get it back to the way it’s supposed to look. It would be great if there was was something to outline all the things that will be affected by this update. The links provided don’t seem to cover any of this.

    Thank you.

      jodie.graves
      Docebian
      • jodie.graves
      • Author
      • Docebian
      • April 24, 2026

      Hey ​@gus - thank you for the feedback! 😊 If you revert back to the legacy interface, you should receive a pop up with a feedback box. This detailed insight is really helpful to the PM’s as we approach that July 22nd date. 
       

      What you’re seeing is expected in the sense that the new navigation introduces updated base styles (typography, buttons, layout), and those can override or bypass some existing custom CSS even when the underlying elements look the same. Our branding/CSS docs do call out that custom CSS is not guaranteed to remain backward‑compatible after new releases, and Support has already confirmed that some CSS which worked with the legacy layout needs updating for the new admin UI specifically. That’s why fonts can suddenly appear bold and border‑radius on buttons can stop applying.

      Right now there isn’t a line‑by‑line public “diff” of every CSS/DOM change (the CSS on your platform will be different to the next persons platform 😬). The available materials focus on:

      • The overall new admin menu experience in the April 2026 release notes (layout, hierarchy, search, accessibility), and

      • The New navigation / branding & CSS docs that explain how custom CSS works and warn about possible breakage with new UI updates.

      To avoid a page‑by‑page clean‑up, the recommended path is:

      1. Keep using the legacy admin menu in production and test the new one only in sandbox (it’s optional until July 22, 2026).

      2. In sandbox, inspect a few representative custom pages with the browser dev tools, identify which global classes/rules are now affecting fonts and buttons, and adjust your custom CSS once at the global level so the fix cascades across all pages. I do appreciate that it will take some time!

      3. If you need to support both legacy and new nav during the overlap, add complementary selectors that also target the new structure, so a single CSS update can handle both layouts.

      If you run into anything that looks like a true regression (rather than just a custom CSS override), I’d definitely suggest logging a ticket with before/after screenshots and your current CSS so Support can confirm whether it’s a bug or expected behaviour 😊

      Thanks!
      Jodes

      T
      Novice II
      • tpendev
      • Novice II
      • April 30, 2026

      Hello,

      What is the procedure to Opt-out of the New Navigation changes. We do NOT wish to ever change to the new UI.

      There are millions of reasons why, however the most important ones are- we spent years of trying to fit the Docebo UI to our branding to look as part of our website, we have extensive custom CSS code, the new UI doesn’t fit our branding, we’ve already trained and spent hours creating training videos for our users, admins and Power Users showing our current UI. There are many more, including the new UI is confusing.

      Thanks in advance!

        G
        Helper I
        Forum|alt.badge.img
        • gus
        • Helper I
        • June 10, 2026

        Hi ​@jodie.graves . Are you able to confirm that what we’re seeing now in the sandbox is set in stone for the July release? We need to recreate our user and power user ‘how to’ courses to reflect the new appearance, layout and behaviours, and I want to be sure I don’t spend the time doing this if things are going to change again. Also, is there yet a document anywhere of all the specific changes? Cheers.

        Terms & ConditionsAccessibility statement