Admins Can Now Gate NetSuite Next Access Per Role

What changed

A new administration page — Manage Access to NetSuite Next — is available to the Administrator role. It provides per-role control over whether users land in the NetSuite Next experience or remain on the classic UI.

Each eligible role can be set to one of three access levels:

• NetSuite Next only — the role is forced into NetSuite Next on the next login. There is no toggle back to classic.
• Optional — users on that role can switch between classic NetSuite and NetSuite Next at will.
• Blocked — the role stays on classic NetSuite with no access to NetSuite Next.

Settings can be applied to individual roles or in bulk.

Ineligible role center types

Roles that use any of the following center types are not eligible for NetSuite Next and will not appear on the management page:

• Advanced Partner Center
• Customer Center
• Employee Center
• Partner Center
• Vendor Center

This means portal-facing and external-user roles remain on the classic UI for now. Only internal roles with standard center types can be toggled.

What is unclear

The source does not specify which NetSuite release introduced this page, and it is described as part of a phased rollout — your account may not have it yet. There is also no documentation on whether this setting is exposed via SuiteScript (e.g., N/runtime or N/config), REST, or SOAP, so scripted role provisioning workflows cannot programmatically set these values until Oracle confirms API coverage.

There is no indication whether the access setting is stored as a field on the Role record or in a separate system table. If you manage roles through custom scripts or bundles that create/modify roles, verify manually whether the new setting persists through those workflows.

What to do

1. Check eligibility. Look for in-app notifications indicating your account has been enabled for NetSuite Next. Only then will the Manage Access page be available.
2. Audit your roles. Before toggling any role to NetSuite Next only, confirm that all workflows, Suitelets, client scripts, and portlets used by that role render correctly in the NetSuite Next UI. Script-injected UI elements and some custom forms may behave differently.
3. Start with Optional. Set key internal roles to Optional first so users can report issues while retaining a fallback to classic.
4. Exclude external roles by design. Portal roles (Customer Center, Vendor Center, etc.) are already blocked. No action needed for those, but be aware that if you have custom center types mimicking these patterns, their eligibility status is undocumented.
5. Monitor scripted role management. If you create or modify roles via SuiteScript or CSV import, test whether the NetSuite Next access setting defaults or resets during those operations.