Customizing or Creating NetSuite Roles

To create a new custom role that tailors the level of access you want to give to users, you can customize a standard role or create a new role. Complete the following tasks:

• Customizing and Creating Roles

• Entering Basic Role Information

• Assigning Core Administration Permissions

• Restricting Role Access to Accounting Books

• Restricting Role Access to Subsidiaries (OneWorld Only)

• Setting Employee Restrictions

• Setting Department, Class, and Location Restrictions

• Setting a Role as Issue Role for Issue Management

• Setting a Role as Web Services Only Role

• Setting a Role as Single Sign-On Only Role

• Restricting a Role by Device ID

• Restricting a Role by IP Address

• Setting Two-Factor Authentication Requirements

• Setting Permissions

• Setting Default and Restricted Forms

• Setting Search Defaults for a Role

• Setting Role-Based Preferences

• Translating Custom Role Names

• Selecting a Dashboard for a Role

After you create a custom role, you can assign it to users. A role's assigned users are listed on the Users subtab of the role record. See NetSuite Users Overview.

Role customization functionality varies according to the NetSuite product you have purchased and the features you have enabled. Some of the fields described in the steps below may not be available to you. For example, location restrictions are not available for NetSuite Small Business users. Also, because of their design as limited access roles, Retail Clerk roles, unlike other standard NetSuite roles, cannot be customized. For details, see Retail Clerk Roles.

You can apply the class, department, location, and subsidiary restrictions that you define here to custom records. See Applying Role-Based Restrictions to Custom Records.

Be aware that updates made to the default role are not pushed to custom instances of that role. You must manually update custom roles to include new default role functionality. Additionally, when a new feature is enabled for an account, permissions associated with that feature are not automatically given to custom roles that existed prior to enabling the feature. These permissions must be manually assigned to custom roles that existed prior to enabling the feature.

General Notices