Services · Streamline & Outsource

Role-based home page customisation: publish NetSuite dashboards by role

When your team log in to NetSuite, the first page they see should be worth looking at. We publish a dashboard to each role and agree what’s fixed and what people can change themselves, so every home page is useful, consistent and maintained in one place rather than user by user.

Published per roleLocked core, personal edges
The problem

Well-designed dashboards are wasted if they are not published to the right roles

You can build good dashboards and still find most people never see them. They log in, land on NetSuite’s default page and carry on as before. Publishing is the step that fixes that. It decides which roles get which page, what’s fixed, what people can change themselves and how an update reaches everyone without someone visiting each login. It’s how the dashboards from our design service end up in front of the people they were built for. And once it’s set up, changing a page later takes minutes, because everything is maintained in one place.

What we run

How we publish NetSuite dashboards to role-based home pages

Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.

  • A page for every roleEvery role is assigned its landing page, a role-based NetSuite dashboard, so each team gets the screen built for it and roles without one get a sensible default.
  • Publishing configurationDashboards are pushed through NetSuite’s Publish Dashboard feature, so each role’s home page is set centrally rather than user by user.
  • What’s locked, what’s personalWe agree which parts of the page are fixed and which users can change, role by role, and write the choice down.
  • Updates reach everyoneChanges are made centrally and released on a known schedule, so an improvement reaches every home page at once.
  • New-starter defaultsPublishing is built into the new-starter setup, so each joiner lands on the right page from their first login.
  • Checking pages get usedWe measure how many people use their home page and how many skip past it, so pages are tuned on evidence.

Everyone landing on the same home page?

We publish role-based dashboards so each team opens what it needs. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.

The payoff

What handing it over buys you

Dashboards reach the people who need them

Publishing puts each finished dashboard in front of the users it was built for.

Key content can’t be deleted by accident

Locked sections protect the important rows while personal areas stay flexible.

One change updates everyone

A single central change reaches every published home page.

New starters see the right page from day one

Joiner defaults make the new starter’s NetSuite home dashboard useful from their first login.

How handover works

From role mapping to central maintenance

  1. Map the roles – each role is matched to its dashboard.

  2. Set the boundaries – locked and personal areas are chosen for each type of role.

  3. Publish in stages – the rollout goes team by team, with feedback gathered as it lands.

  4. Maintain centrally – updates go out on a known schedule and use is watched.

Good to know

What to know before you hand it over

  • !What to lock is your organisation’s choice, and we set out the options. Fully locked pages can feel restrictive to users, while fully open pages drift away from the design. The balance for each type of role is your choice, and we’ll set out the trade-offs plainly.
  • !NetSuite’s publishing feature has quirks. How updates interact with users’ own changes follows NetSuite’s publishing model, so we design around how it really behaves and explain it plainly during rollout.
  • !Adoption depends on relevance, so we measure it. We watch how often pages are skipped, and a published page people skip is treated as a design problem to fix rather than a success.
Straight answers

Role-Based Home Page Customisation FAQs

Can users still add their own portlets?
Yes, and that’s the point of agreeing what’s locked and what isn’t. Usually the top of the page is fixed, so the KPI row and the key worklists are always there, and the lower half is left free for people’s own shortcuts and saved searches. We agree that split for each type of role and write it down.
How do updates reach already-published pages?
We make the change once, on the central page, check it, then push it out to everyone who has that page. Updates go out on a known schedule, and people are told what’s changing and when, so nothing on their home page moves around as a surprise.
What about users with multiple roles?
A NetSuite user with several roles works in one role at a time, and the home page simply follows the role. Switch into purchasing and you see the purchasing page; switch back to finance and the finance page returns. We check that every role someone uses has a proper page, so nobody with a second role is left looking at a default.

Last reviewed: 21 October 2026 · Written by the Suite Generation team

Ready to hand this one over?

Tell us the roles involved and the problems you are seeing. We will scope the work and give you a straight answer on effort.

Scoping Call — Sitewide

We reply within 24 hours.

or email hello@suitegeneration.net

Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.

Independent – no licence resellingSenior-led – solution-architect levelTrusted to fix failed implementations
Talk to a solution architect