In most Adaptive Planning tenants we work on, users keep jumping around. The sheet is in one menu. The report is in another. The dashboard is somewhere else. The instructions for the budget cycle sit in an email. So every cycle, people ask the same question: where do I go and what do I do?
Hubs solve this.
What a Workday Adaptive Planning Hubs is
A hub is one workspace where we keep everything a user needs for their planning work. Dashboards, sheets, reports, links, and tasks all sit in one place. Workday introduces Hubs in the 2026 R1 release.
An admin builds the hub and shares it with the right people. So the finance team gets a Finance Hub, the sales team gets a Sales Hub, and each team sees only what is relevant to them. A hub can also follow a process instead of a team, like a Workforce Management Hub.
Hubs do not change security. They follow the existing Adaptive access rules, so users still see only the data they already have access to.
Turning it on
Hubs work through permissions. There are two to know:
Access Hubs lets a user open and view hubs.
Edit Hubs lets an admin create, edit, clone, share, and manage hubs.
To switch it on, the admin goes to Administration, then Permission Sets, edits the permission set, and selects Access Hubs and Access Dashboards. Edit Hubs goes only to the people who build hubs. After this, Hubs shows up in the main menu.
Creating a hub
The admin selects Hubs from the main menu and clicks + New Hub. They give it a name, like “Finance Hub”, and a short description if needed.
The new hub opens in edit mode with an overview page that already has three widgets: a Text widget, a Performance Summary, and a Workflows widget once Configurable Workflows is set up. We use the text widget to tell users what to do, by when, and where to start.
Sharing a hub
First we save the hub as a draft. Nobody sees it yet. When it is ready, we go to Administration, Hubs, Manage Hubs, pick the hub, and choose the users or groups under Available To.
When we share with a group, any new member of that group gets access automatically. When we remove someone, they lose access right away.
Using it day to day
Users can set a shared hub as their default home page. So when a planner logs in, they land straight in their hub. The home page also shows up to three recent hubs.
When we need to make a big change to a live hub, we check it out. This creates an editable personal copy while the shared version keeps working for users. If we unshare a hub, it goes back to Personal and disappears from users’ home pages.
For regional teams, we clone a hub instead of building again. For example, Finance Hub North America and Finance Hub EMEA.
What is new in 2026 R2
Grouped filters keep selections like version and level in sync as users move between hub pages. So nobody resets the same filter on every page.
Each hub gets a files area for supporting documents like spreadsheets, presentations, and PDFs.
Users can create, edit, share, and merge scenarios from inside the hub.
The text widget now supports formatting, links to sheets, reports, and dashboards, and images.
How we suggest starting
Start with one hub for one team, like a Financial Planning Hub, and test it with a few groups first. Keep only what people really need in it. Use the same layout across hubs so users always know where things are. When we clone a hub, we check the links, widgets, and permissions again. And we archive old hubs instead of deleting them.
Our take
A hub does not add new planning logic. It changes how people find and follow the work. For a budget cycle with many contributors, that alone saves a lot of back and forth.