Your Role Permissions Are Now Your AI Policy
Ask Oracle and NetSuite's new agents run under your existing roles. In most accounts those roles are a mess, and the AI inherits all of it.

NetSuite's answer to "can we trust the AI" at SuiteWorld was simple. Ask Oracle and the new agents run under the same roles and permissions your people do. If a user can't see payroll, the AI can't show it to them.
That's the right design. It's also a problem, because in most NetSuite accounts the roles are a mess. The AI doesn't fix that. It inherits it.
What roles look like in most accounts
If your account is more than a couple of years old, odds are good you'll find some of this:
- Administrator handed out as a fix. Someone couldn't do something, so they got Admin. Nobody took it back.
- Copy-of-a-copy roles. "Custom AP Clerk (2)" built from "Custom AP Clerk," built from the standard role, each with a few extra permissions added to solve one ticket.
- Full access where View was enough. It was faster than figuring out which level the user actually needed.
- Roles assigned to people who left. Or to integration users nobody can explain.
None of this felt urgent before. A person with too much access mostly sticks to their own work, because finding the other stuff takes effort.
Why it matters more now
AI removes the effort. That's the whole point of it.
Before, an over-permissioned warehouse lead would have to know a saved search existed, find it, and run it to see margins by customer. Now they can just ask. Ask Oracle will gather the data, do the analysis, and hand it back with links to the records. All of it is perfectly within that person's permissions, and none of it is anything you meant them to see.
Agents raise the stakes again. NetSuite was clear that agents can create draft records and take actions, with approvals where you require them. Every agent runs with a set of permissions. If you build those the way your people's roles were built, you'll get the same results, only faster.
The new SuiteAgent Management Workspace shows what agents are doing and what data they touch, and you can switch any of them off. That's useful. But it shows you the problem after it happens.
What to check before you turn it on
This isn't a six-month security project. It's a few saved searches and some uncomfortable conversations.
- List everyone with Administrator. It should be a short list. If it isn't, start there.
- Find the copy-of-a-copy roles. Compare custom roles against the standard role they came from. Most of the drift is in the extras.
- Look hardest at sensitive records. Payroll, employee records, compensation, customer pricing, margins. Who can see them, and should they?
- Clean up inactive users and integration roles. If nobody can say what a role is for, remove it and see who complains.
- Build agent permissions from zero. Don't clone a human role for an agent. Give it exactly what its job needs and nothing else.
Bottom Line
The pitch at SuiteWorld was that trust comes before automation. Your role setup is where that trust actually lives.
Fix it first, and Ask Oracle becomes a tool people can rely on. Skip it, and it's a very fast way to find out who has access to what.
Dealing with this in your own NetSuite account?
We fix exactly these problems in production. Run a free read-only health scan, or talk to a senior NetSuite consultant who has seen it before.
Written by Mike Pagani, founder of Adaptive Solutions Group — a NetSuite consultancy based in Pittsburgh, PA. Mike has been building SuiteScript automations, integrations, and NetSuite rescue projects since 2013.