Department, Class, and Location Restrictions in NetSuite

Restricting access based on Departments, Classes, and Locations enhances security and data management in NetSuite. Administrators can set these restrictions per role, ensuring that users only see the relevant data they are authorized to view. This setup is particularly useful for organizations with multiple departments and functions, facilitating better data governance and compliance practices.

How To Set Restrictions on Departments, Classes, and Locations

To apply these restrictions, follow these steps:

1. Navigate to the Restrictions subtab for the role you wish to edit.

2. Configure the following settings:

   Field	Description
   Segment	Select either Class, Department, or Location to apply the restriction.
   Restrictions	Choose a restriction level:

   • none - default to own: No selection restrictions; defaults to the current user.
   • own, subordinate, and unassigned: Users can view records for their own department/class/location and both subordinate and unassigned records.
   • own and subordinates only: Users can only view their own and subordinate records without including unassigned records. | Allow Viewing | Enables users to see data for restricted Departments, Classes, and Locations without editing privileges. Note this excludes payroll or commission details, and non-subordinate records are visible only if they directly match. | | Apply To Items | Extend the same restrictions to item records as well. |

Important Considerations

• Accounts in the Chart of Accounts with no assigned department are not subject to the own, subordinate, and unassigned or own and subordinates only restrictions.
• In NetSuite OneWorld, subsidiary restrictions automatically relate to departments, meaning users restricted to a subsidiary will only have access to departments linked to it, enhancing the compartmentalization of data.

Custom Records and Role-Based Restrictions

Role-based restrictions can also be applied to custom records by checking the Apply Role Restrictions box for custom fields corresponding to these categories. This ensures users with specific roles only interact with relevant custom records.

Who This Affects

This update primarily impacts the following roles:

• Administrators: To set and manage restrictions effectively.
• Users with Custom Roles: Ensures they operate under the security policies defined by administrators.
• Accountants and Managers: To enhance oversight and compliance within departmental confines.

Key Takeaways

• Role-based restrictions enable tailored access to departmental data in NetSuite.
• Administrators can define specific levels of access for each role, enhancing security.
• Restrictions on non-assignable records streamline data visibility, preventing leaks to unauthorized users.

Source: This article is based on Oracle's official NetSuite documentation.