Summary. Hiding a field in NetSuite, on a form or with a workflow or script, changes what the screen shows. It does not change what the role can read. A role that can view the record can usually still reach the field through saved searches, reports and queries. That has always been true. AI makes it easier to run into: an assistant connected through the NetSuite AI Connector works through the user’s role, and a routine question can bring back a detail nobody asked for. Before you connect a role, find out what it can actually reach.
Hiding a field is a display setting
Fields usually get hidden in one of two ways:
- Hidden by default, then shown for some users by a workflow or a user event script.
- Shown by default, then hidden for some users by a user event script before the page loads.
A custom form can also leave the field off or set it to hidden. All of these change what the form shows. None of them changes what a saved search, a report, a query or an AI answer can return for that role. Item cost is the example used here, but the same applies to commissions, vendor pricing, margins, pay rates or any field you’d rather some roles didn’t see.
Where the data is still reachable
A user with the required search and record permissions may be able to retrieve item cost or preferred vendor through a saved search. Reports and SuiteQL queries provide other access paths, subject to the connected role’s permissions.
What AI changes
This is not AI getting around permissions. It is AI using access the role already had, through a path nobody had to think about before.
Oracle describes the AI Connector as role-based: the tools a user sees, and the data they can reach, depend on the permissions of the role they connect with. Its standard tools include saved searches, reports and read-only SuiteQL queries. Oracle’s documentation adds a detail worth knowing. The connector’s saved search tools need the Perform Search permission, but its SuiteQL query tool has no specific permission requirement: what it returns depends on the role’s existing permissions. So a role that cannot run saved searches may still reach the same fields with a query.
Routine questions can expose sensitive data
A saved search returns its defined columns. An AI assistant may retrieve additional fields while answering a question. For example, a sales rep asking whether an item is in stock could receive its cost in the same response. Whether that field is accessible depends on the connected role, even if the sales form hides it.
Illustration: a hypothetical answer, not a recorded one.
What to check, role by role
- List the fields you treat as sensitive: cost, margin, commissions, vendor and purchase price, pay rates, customer pricing.
- Find where they are hidden today: forms, workflows and scripts.
- For each role you plan to connect, test whether those fields can be reached by saved search, report, query or the AI Connector.
- Separate real controls from display settings. Custom fields have a field-level control: the Default Level for Search/Reporting on the field’s Access subtab (None stops searches and reports returning it). Many standard fields, such as item cost, have no field-level permission. Whether a role can read them depends on its access to the record, so test the role rather than assume.
- Decide, role by role, whether to connect it knowing what it can reach. Not every exposure has a clean fix, and removing record access can take away what people need to do their jobs.
- Re-check after any role or permission change, and before adding a role to the AI Connector.
If you need to limit the AI channel
One architectural option is a purpose-built custom tool that returns only approved fields, with the broad built-in tools turned off and no other installed tool that can query freely. It limits what the assistant can retrieve. It does not change what the role can read in saved searches, reports or exports, and it needs testing in your account before you rely on it.
How YTBE helps
This is part of our AI readiness check. We find where your account hides fields, test what each role can actually reach by search, query and the AI Connector, and show you which controls are real and which are display only, so you can decide with the facts. We do it in your sandbox first.