A NetSuite access review should establish what each person and integration needs to do, which records they should see, and whether their effective access matches that need. Reviewing role names alone is insufficient. Permissions, restrictions, global permissions and reporting options can combine to produce access that a simple role list does not explain.
Begin with a business responsibility and a representative task. Then test both the action that should work and the action that should be denied. This approach produces a review that finance, operations and system administrators can understand together.
Separate actions from record scope
Oracle distinguishes permissions and restrictions. Permissions govern access to record types or tasks; restrictions narrow the records available within that access. A person may need to edit a transaction type while being limited to particular subsidiaries or other permitted business dimensions.
Write the requirement in those two parts. For example, “enter vendor bills for the assigned entity” contains both an action and a scope. “Finance access” does not. Document whether the person needs to create, view, edit or perform another supported action, and then define the relevant population.
Account configuration matters. OneWorld, custom records, enabled features and installed applications can change the permissions and restrictions that must be reviewed. Use current documentation and the actual account configuration rather than assuming that a standard role name has the same effective reach in every business.
Build an access inventory with owners
List active employees, external users where applicable, integration identities and privileged accounts. Associate every identity with a current owner, purpose and review date. Include assigned roles and any global permissions that may affect access independently of a selected role.
Do not treat an integration identity as an ownerless technical exception. Record the business process it supports, the system that uses it and the person accountable for its permissions. Keep secrets out of the review workbook. The inventory needs references to approved credential ownership, not passwords or tokens.
For each role, identify the business owner and the administrator responsible for implementation. Record the expected user population, sensitive tasks, restrictions, custom records and reporting dependencies. A role copied several years ago can retain capabilities that its current name no longer suggests.
Create the role and set its permissions
Have the account administrator implement the approved access design. Product features and custom records affect which permissions and restrictions are available.
- Open Setup > Users/Roles > Manage Roles. Choose Customize beside a suitable standard role, or New for a new role. Name it and review the center type and inherited permissions.
- On the Permissions subtab, add or remove only the approved permissions and select the required level. Configure the relevant subsidiary, employee and other restrictions separately.
- Save the reviewed role, assign it through the authorized user-access process, and test allowed and denied actions with the intended identity. Recheck saved searches and exports as part of the same acceptance.
A customized copy can inherit excessive access, so copying a role is a starting point for review.
Review combinations that create risk
Look at the complete sequence of a business transaction. Can one person create a vendor, change payment details, enter a bill and authorize payment? Can someone both adjust inventory and approve the correction? The right separation depends on the organization's size and controls, but the combined capability must be visible.
Where staffing prevents strict separation, document compensating review and its evidence. An independent review of changes or payments can be appropriate when finance approves the design. Avoid describing an access setting as proof of compliance without considering how the process operates.
Privileged access deserves a separate discussion. Define when administrators should use elevated roles and how exceptional changes are reviewed. Do not expand ordinary user permissions merely because a test succeeds as Administrator. First establish the smallest role and record scope that support the intended task.
Include reports and saved searches
A record form is only one route to information. Review saved searches, workbooks, exports, scheduled emails and any custom reporting interfaces used by the role. Ask who receives the output and whether it includes data outside the intended population.
Oracle's Run Unrestricted guidance is especially important for saved searches. That option can override role restrictions in search results while required permissions still apply. The result list and the ability to drill into an underlying record are separate questions. Test both rather than assuming one successful or denied action settles the whole issue.
Similarly, sharing a workbook or dataset does not grant missing record or field permissions. Two recipients may legitimately see different results. Reviewers should distinguish a data-access problem from a reporting-definition problem before changing permissions to make totals match.
A hypothetical finance access review
Consider a fictional group with separate operating subsidiaries. A billing specialist needs to create invoices for one entity and view related customer balances. The role was copied from a broader finance role and also includes unnecessary access to vendor maintenance.
The reviewer first tests the intended invoice process using representative permitted records. Next, they try another entity's transaction and confirm that the configured restriction works. They examine a saved search used by the specialist and discover that its unrestricted-result setting needs separate review. Finally, they remove the unused vendor-maintenance capability through the approved change process and rerun the invoice tests.
This example does not prescribe the exact NetSuite permission levels for every account. Its lesson is the sequence: establish business need, inspect effective access, test allowed and denied cases, approve the change, and verify that necessary work still succeeds.
Use a review record that can be repeated
A practical access-review record contains:
- Identity or role and current business owner
- Business task and expected record population
- Permission and restriction being evaluated
- Allowed test and denied test with observed results
- Reporting, export and integration dependencies
- Conflict or unnecessary capability identified
- Approved remediation and implementation owner
- Retest evidence and completion date
Retain the evidence in an access-controlled location. Screenshots and exports can themselves contain sensitive business information. Limit them to what the reviewer needs and use permission-cleared examples when creating training or public material.
Handle joiners movers and leavers
New starters should receive access based on their current duties. A move between teams should trigger a review of old responsibilities as well as new ones. Removing an employee's old role is easy to overlook when the request is framed only as adding access.
For departures, follow the approved offboarding process and examine ownership of searches, workflows, integrations and scheduled activity. Removing a person's access can expose an undocumented operational dependency. Transfer legitimate ownership through the appropriate controlled process rather than retaining unnecessary personal access indefinitely.
Set review frequency according to risk and business change. Acquisitions, new subsidiaries, reorganizations, integration changes and sensitive incidents may justify an additional review between scheduled cycles. A dated sign-off has little value if the account has materially changed since it was performed.
Does sharing a report grant access to its underlying records?
Do not assume so. Oracle documents separate sharing and record-permission behavior. Test the recipient's effective role, result visibility, exports and drilldown using the actual report design.
A practical role review finishes with understandable business responsibilities and tested access boundaries. The useful result is a smaller, explainable permission set that still lets people complete their work.
Related resources