Restricting Access to Records by Class
If your account has the Classes feature enabled, you can restrict access to transaction, employee, partner, and optionally item records based on their assigned class values. You can also limit the classes that users can assign to these records. Class restrictions can be defined per user role and then applied to all users logged in with that role.
Any account in the Chart of Accounts list that does not have an assigned class is not subject to the own, subordinate, and unassigned or own and subordinates only restrictions.
The following settings for the Class Restrictions field on the Role page define class-related restrictions for transaction and customer records:
-
none -no default – There is no restriction on what can be selected. Record access is not determined by this field. A default selection does not appear.
-
none -default to own – There is no restriction on what can be selected. Record access is not determined by this field. Fields of this type will select the user by default.
-
own, subordinate, and unassigned – Users are restricted to records with their own class, children records of their class, and records with unassigned class field. For example, if your role has access to class A, you can only see records in class A, as well as its children or unassigned records.
-
own and subordinates only – Users are restricted to records with their own class and children records of their class. For example, if your role has access to class A, you can only see records in class A, as well as its children.
Check the Allow Viewing box to permit users logged in with this role to see, but not edit, records for classes to which the role does not have access.
Check the Apply to Items box to apply the class restrictions defined here to item records, in addition to transaction and customer records.
To set up a role to include these restrictions, go to Setup > Users/Roles > Manage Roles. Click Customize or Edit, or click the New button.
In NetSuite OneWorld, subsidiary restrictions automatically apply to classes. For example, if Class A is assigned to only Subsidiary X and a role is restricted to Subsidiary X, users with that role have access to only Class A, even if that role does not have any class restrictions.
If you are using the Advanced Employee Permissions feature, restrictions set on the Role page are only applicable to the Employees and Employee Administration permissions. The Employee Public and Employee Confidential permissions ignore the restrictions set on this page. For more information, see Setting Employee Access for Advanced Employee Permissions.
You can also apply role-based, class restrictions to custom records. For more information, see Applying Role-Based Restrictions to Custom Records.