Study guide
16.1 What a Custom Role Can See and Do
Oracle NetSuite SuiteFoundation Specialist Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction and Exam Facts
1.1 Current Exam Facts 1.2 The 2025 Program Change and Keeping the Credential 1.3 The Five Weighted Domains and How to Study Them
2 Enable Features and Renaming Records
2.1 What Enable Features Controls 2.2 Renaming Records and Transactions
3 Support-Only Features and Classifications
3.1 Features That Need NetSuite Support 3.2 Classifications and Subsidiaries
4 SuiteBuilder and Platform Tools
4.1 Custom Forms, Fields, Records, and Subtabs 4.2 Bundles, SuiteApps, and SuiteFlow
5 Navigation, Performance, and Preferences
5.1 Roles, Centers, and Navigation Tools 5.2 Browser Experience and Performance 5.3 User Preferences That Change the Interface
6 Shortcuts, Activities, and the File Cabinet
6.1 Shortcuts Portlet versus the Shortcuts Menu 6.2 Activities, Email, and the File Cabinet
7 Sales Cycle, Quotas, and Forecasts
7.1 Setting Up Sales Force Automation 7.2 Leads, Prospects, and Customers 7.3 Quotas and Forecast Reporting
8 Cases and Marketing Campaigns
8.1 Case Management Setup and Use 8.2 Campaigns and SuitePromotions
9 Sales Orders, Fulfillment, and Payments
9.1 Sales Orders and General Ledger Impact 9.2 Fulfillment Controls 9.3 Customer Payment Methods
10 Returns, Credits, and Refunds
10.1 Return Authorization Forms and Ledger Impact 10.2 Return Controls and Refunds
11 Item Types and Inventory
11.1 Item Types and Best Uses 11.2 How Transactions Change Inventory Levels 11.3 Advanced Inventory Features
12 Pricing, Billable Costs, and Payables
12.1 Sales Pricing Options 12.2 Billable Time and Expenses 12.3 Purchase Approval Routing 12.4 Accounts Payable Steps and Ledger Impact
13 Finding Records and Saved Searches
13.1 Global Search, Lists, and Reports 13.2 Elements of a Saved Search
14 Portlets and Data Management Tools
14.1 Portlet Types 14.2 Inline Editing, Mass Update, CSV, and Duplicates
15 Support, Help Resources, and Releases
15.1 Working with NetSuite Support 15.2 Where to Look Up a Feature 15.3 Release Cycles and Release Preview
16 Custom Roles and Data Access
16.1 What a Custom Role Can See and Do 16.2 Building Roles Instead of Sharing Administrator
17 Authentication, Security Questions, and Settings
17.1 Passwords and Two-Factor Authentication 17.2 Security Questions 17.3 The Settings Portlet
18 Tracking Changes to Records
18.1 System Notes and Other Audit Tools 18.2 Ledger Impact and Field-Type Changes
16.1 What a Custom Role Can See and Do
Key Takeaways Explain This Topic AI
View, Create, Edit, and Full are the permission levels: Create can add and view records but cannot edit them, and Edit can create and change records but cannot delete them.
A global Edit permission on one employee's record adds Edit for that employee. The shared role's Create permission still lets that employee create records.
Subsidiary restrictions default to User Subsidiary. Department, class, and location restrictions use none - no default, none - default to own, own, subordinate, and unassigned, or own and subordinates only.
Accounts on the chart of accounts with no department or class stay visible under those segment restrictions, so account access is wider than the restriction line suggests.
Import CSV File and Export Lists are separate permissions. Full CSV Export remains available only to the Administrator role.
Last updated: September 2026
Data access by role
A custom role controls data access by role in two layers. A permission decides what the user can do with a record type, a task, or a page. A restriction decides which records of that type the user can reach. Oracle NetSuite Help documents the working levels as View, Create, Edit, and Full. None, where the list offers it, grants no access. CSV import and CSV export are separate permissions, not a side effect of Edit or Full.
Open the role from Setup > Users/Roles > Manage Roles. Click Edit on a custom role, or Customize when you start from a standard role. Permissions are grouped on Transactions, Reports, Lists, Setup, and Custom Records. Each line has its own level.
What each permission level allows
Help defines the levels as a ladder. A higher level adds actions. It keeps the actions of the levels below it.
View lets the user see existing records only. The user cannot create, change, or delete a record.
Create lets the user create new records and view existing records. The user cannot edit an existing record and cannot delete one. Create does not include Edit. A role with Opportunities set to Create can enter a new opportunity and can open one that already exists. Saving a change to that existing opportunity requires Edit or Full.
Edit lets the user create new records, view existing records, and edit existing records. The user cannot delete them. Edit includes creating new records, so a user at Edit can still create. Raising a permission from Create to Edit adds the ability to change existing records and leaves creation in place.
Full lets the user create new records and view, edit, and delete existing records. A few permissions do not follow this ladder. Export Lists, for example, has only the Create level.
Level What the user can do to a record
View View existing records only. Cannot create, edit, or delete. Printing is generally available at View.
Create Create new records and view existing records. Cannot edit or delete. Create does not include Edit.
Edit Create new records, view existing records, and edit existing records. Cannot delete.
Full Create new records and view, edit, and delete existing records.
Global permission Adds the level stored on that employee's record. It does not replace the role with a lower level, and it is ignored for the Administrator role.
Global permissions add access for one employee
Global Permissions is optional, and Help describes it as not the preferred way to grant access. Enable it at Setup > Company > Setup Tasks > Enable Features, on the Employees tab. The employee record then has a Global Permissions subtab under Access. Select a permission and a level of View, Create, Edit, Full, or None.
The employee still needs a role on the Roles subtab. At login, the permission set is a combination of the global permissions and the role in use. Global permissions are ignored for the Administrator role, and they cannot reduce Administrator access.
Two users can share a role whose Opportunities permission is Create. The first user has no global permission for Opportunities. That user can create opportunities and view them, and cannot edit an existing opportunity, because Create does not include Edit. The second user has the same role and a global permission of Edit for Opportunities on the employee record. That user can edit existing opportunities and can still create them. Edit includes creating new records, and the global permission adds Edit for that user only. It does not replace the shared role with a lower level, and it does not remove Create. The first user is unchanged, because the global line sits on the employee, not on the role. Edit includes create. It adds the ability to change existing records.
Restrictions on which records appear
A permission grants the record type. A restriction decides which instances the user can access. In OneWorld, set subsidiary limits under Subsidiary Restrictions. Set department, class, and location limits on the Restrictions subtab, and employee limits in Employee Restrictions. The same limits can apply to a custom record when Apply Role Restrictions is checked on a list or record custom field. Users already logged in must log out and back in before new permissions or subsidiary restrictions apply.
Subsidiaries
In NetSuite OneWorld the default is User Subsidiary. The user sees the subsidiary on the employee record, so two people who share a role can still see different subsidiaries. Active grants active subsidiaries only. All includes inactive subsidiaries. Selected grants the subsidiaries you pick on the role.
Allow Cross-Subsidiary Record Viewing lets the role see, but not edit, records in subsidiaries it is not granted. That box cannot show employee payroll or commissions.
A subsidiary restriction also narrows departments and classes. When a department belongs only to one subsidiary and the role is limited to that subsidiary, the user can use the department even with no separate department restriction. A role can edit a department only when it can reach every subsidiary assigned to that department.
Departments, classes, and locations
With Departments, Classes, or Locations enabled, these limits cover transaction, employee, and partner records, and item records if you apply them to items. They also limit which segment values the user may assign. Choose the segment, then a level:
none - no default leaves the segment unrestricted and fills no default.
none - default to own leaves the segment unrestricted and defaults new records to the user's own department, class, or location.
own, subordinate, and unassigned limits the user to that segment, its children, and records where the segment is blank.
own and subordinates only limits the user to that segment and its children, and hides records where the segment is blank.
Allow Viewing lets the user see, but not edit, values outside the restriction. It does not reveal payroll or commissions. At own and subordinates only, the user still cannot view non-subordinate records other than the user's own.
An account with no department, or no class, sits outside own, subordinate, and unassigned and outside own and subordinates only. The segment restriction does not hide it. Limit accounts by restricting the account records and the role together.
Employee restrictions
Employee Restrictions use the same four values. They limit transaction, customer, and employee records by the employee, sales rep, and supervisor fields, and they do not limit contacts. The two tighter values let the user select only self or subordinates. Own, subordinate, and unassigned still shows records with nobody in that hierarchy. Own and subordinates only hides them. Allow Viewing shows other employees without edit rights and still blocks payroll and commissions.
When Advanced Employee Permissions is on, Employee Self, Employee Public, Employee Confidential, and Employee Compensation ignore these role-page limits. The Lists permission Employees overrides them with full employee-record access. Remove Employees when the role should see only part of the record.
Restricting CSV import and export permissions
Import CSV File and Export Lists are different permissions. Granting one does not grant the other, and neither belongs on every role.
Import CSV File is a Setup permission. Most Import Assistant record types require it. The role still needs the record permission for the file. A journal-entry import needs Make Journal Entry at Edit or Full together with Import CSV File.
Export Lists is a Lists permission with only the Create level. It adds Export and Email on search and saved-search results for record types the role can already open, and it requires Perform Search at least at View.
Full CSV Export , at Setup > Import/Export > Export Tasks > Full CSV Export, is limited to the Administrator role. Export Lists does not turn that task on.
Leave both off roles that only enter or review transactions. An import writes many records in one job, and a downloaded export is no longer filtered by subsidiary, department, class, location, or employee. When you customize a standard role, remove these lines unless that job loads or extracts files.