Advanced Employee Permissions
Advanced Employee Permissions
Advanced Employee Permissions
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted
in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end
users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed
on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks
of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc.
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
This documentation is in pre-General Availability status and is intended for demonstration and preliminary
use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to
this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of
this documentation.
The information contained in this document is for informational sharing purposes only and should be
considered in your capacity as a customer advisory board member or pursuant to your pre-General
Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any
features or functionality described in this document remains at the sole discretion of Oracle.
This document in any form, software or printed matter, contains proprietary information that is the
exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms
and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle
PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has
been executed by you and Oracle and with which you agree to comply. This document and information
contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle
without prior written consent of Oracle. This document is not part of your license agreement nor can it be
incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website
at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Sample Code
Oracle may provide sample code in SuiteAnswers, the Help Center, User Guides, or elsewhere through
help links. All such sample code is provided "as is” and “as available”, for use only with an authorized
NetSuite Service account, and is made available as a SuiteCloud Technology subject to the SuiteCloud
Terms of Service at www.netsuite.com/tos.
Oracle may modify or remove sample code at any time without notice.
As the Service is a multi-tenant service offering on shared databases, Customer may not use the Service
in excess of limits or thresholds that Oracle considers commercially reasonable for the Service. If Oracle
reasonably concludes that a Customer’s use is excessive and/or will cause immediate or ongoing
performance issues for one or more of Oracle’s other customers, Oracle may slow down or throttle
Customer’s excess use until such time that Customer’s use stays within reasonable limits. If Customer’s
particular usage pattern requires a higher limit or threshold, then the Customer should procure a
subscription to the Service that accommodates a higher limit and/or threshold that more effectively aligns
with the Customer’s actual usage pattern.
Beta Features
Oracle may make available to Customer certain features that are labeled “beta” that are not yet generally
available. To use such features, Customer acknowledges and agrees that such beta features are subject
to the terms and conditions accepted by Customer upon activation of the feature, or in the absence of
such terms, subject to the limitations for the feature described in the User Guide and as follows: The beta
feature is a prototype or beta version only and is not error or bug free and Customer agrees that it will
use the beta feature carefully and will not use it in any way which might result in any loss, corruption or
unauthorized access of or to its or any third party’s property or information. Customer must promptly
report to Oracle any defects, errors or other problems in beta features to [email protected] or
other designated contact for the specific beta feature. Oracle cannot guarantee the continued availability
of such beta features and may substantially modify or cease providing such beta features without
entitling Customer to any refund, credit, or other compensation. Oracle makes no representations or
warranties regarding functionality or use of beta features and Oracle shall have no liability for any lost
data, incomplete data, re-run time, inaccurate input, work delay, lost profits or adverse effect on the
performance of the Service resulting from the use of beta features. Oracle’s standard service levels,
warranties and related commitments regarding the Service shall not apply to beta features and they may
not be fully supported by Oracle’s customer support. These limitations and exclusions shall apply until the
date that Oracle at its sole option makes a beta feature generally available to its customers and partners
as part of the Service without a “beta” label.
Send Us Your Feedback
We'd like to hear your feedback on this document.
Answering the following questions will help us improve our help content:
■ Did you find the information you needed? If not, what was missing?
■ Did you find any errors?
■ Is the information clear?
■ Are the examples correct?
■ Do you need more examples?
■ What did you like most about this document?
Click here to send us your comments. If possible, please provide a page number or section title to identify
the content you're describing.
This section describes how access to the employee record, using different contexts, changes when the
Advanced Employee Permissions feature is enabled. You should go through the following list before you
enable the feature. If required, complete any of the recommended actions. For more information, contact
NetSuite Customer Support.
When using an account that does not have Advanced Employee Permissions enabled, it is only possible
for employees to perform employee searches when they are assigned to a role that has the Lists >
Employees, Lists > Employee Record, and Lists > Perform Search permissions.
However, when the Advanced Employee Permissions feature is enabled, many standard NetSuite roles
are automatically given the Employee Public and Lists > Employee Record permissions, which gives them
access to perform employee searches. Therefore, it is important that you review existing saved employee
searches and limit access to any searches that are not relevant to some users.
■ Location — Toronto
■ Base Wage — Greater than $100,000
Any employees that do not meet this criteria are filtered out. Only the employees who are located in
Toronto and who have a base wage greater than $100,000.00 are shown in the saved search results. In
the image below, you can see that four employees meet this search criteria.
■ Location — Toronto
■ Base Wage — Greater than $100,000
The search shows different results, as you can see in the image below. This is because the Employee
Public permission does not have access to see the base wage of employees, therefore this filter is not
applied. Instead, this user sees all employee’s that meet the filter criteria of Location — Toronto.
The following section gives examples of how the displayed information changes when using Advanced
Employee Permissions.
Important: NetSuite recommends that when using Advanced Employee Permissions you
should view the Employees List page using the Basic view, instead of the default All view. With the
Basic view, you will see a more extensive list of employees because the basic field set is contained
in most standard employee permissions. With the All view, there are more columns displayed,
however, it may restrict the number of employees you see. For more information, see Example 3
— Employees List View Results with Employee Confidential and Employee Self Permissions.
■ First Name
■ Last Name
■ Email
■ Gender
■ Job Title
With this permission, when the user selects All from the View dropdown list on the Employees List page,
the employees that directly report to the user are shown in the list. In this example, the user has one
direct report and each of the fields that are part of the Employee Confidential permission are shown (First
Name, Last Name, Email, Job Title, and Gender). This is because the Employee Confidential permission has
the default restriction of Subordinates.
■ First Name
■ Last Name
■ Email
■ Job Title
■ Birth Date
With this permission, when the user selects All from the View dropdown list on the Employees List page,
the user sees the fields exposed with the Employee Self permission only for themselves. This is because
the Employee Self permission has the default restriction of Own Only, meaning the user only has access
to this information for themselves on their employee record.
□ Job Title
□ Birth Date
All View
With the Employee Confidential and Employee Self permission combination, when the user selects All
from the View dropdown list on the Employees List page, the user sees an empty list. This is because the
All view on the Employees List page generates the available columns, based on the fields the role has
access to, across all roles, and displays all the employees that match all the fields that the user has access
to. When fields are removed from the view, you will see the following message:
Some fields are hidden because your role does not have permission to view them. To change what you are permitted
to view, please contact your administrator.
Basic View
With Employee Confidential and Employee Self permission combination, when the user selects Basic
from the View dropdown list on the Employees List page, the user sees themselves and their direct
reports. This is because the field set contained in the Basic view is contained in most standard employee
permissions.
If required, move any custom fields from the contact record to the employee record before enabling
Advanced Employee Permissions.
Script Access
The following section outlines how script access changes when Advanced Employee Permissions is
enabled.
The fields and subtabs a user has access to can change depending on which employee record is being
viewed or edited. This is different from other records in NetSuite, where permissions granted to a role
determine just the instances of the record the role can see.
The search columns available to users are also dependent on the permissions assigned to the role.
In general, scripts should always check to see if a field or sublist exists before trying to do something with
it. Simply calling functions and methods that interact with fields and sublists before checking whether
they are there may result in inconsistent behavior.
For example, when the Department field is permitted on the employee record, and you check to see if
this field exists and you do not have access, a null value is returned. If the field is empty, an empty string is
returned.
To check if your role has access to a field for a specific employee, load the employee record object and call
getAllFields().includes(). If the field exists and you do have access, a true value is returned.
In the following example, the user has access to the Department field for the employee with ID:115.
Taking the previous two script examples into consideration, you should use the following example to
make sure your scripts do not fail.
For more information about working with SuiteScript, see the help topics Suitelets and UI Object Best
Practices and Client Script Best Practices.
For more information about workflows, see the help topic Working with Workflows.
■ When a value for a field is set on the employee record in a SOAP web services program, and the
current role does not have access to that field, the program completes without errors, but the field is
not set or updated.
■ For SOAP web services in accounts with Advanced Employee Permissions enabled, fields and subtabs
that the current role does not have access to are not returned through search or filtering.
Custom Roles
Custom roles created in your NetSuite account are not automatically updated with the employee
permissions introduced by Advanced Employee Permissions. Custom roles will need to be manually
updated to include any of the required employee permissions. For details, see Changing Access and
Restrictions for Advanced Employee Permissions.
SuiteBuilder
By default, when Advanced Employee Permissions is enabled, any customization created with NetSuite
SuiteBuilder that are included with the standard Lists > Employees permission are preserved. However,
customizations are not preserved when the Lists > Employees permission is customized. If required,
you will need to manually add customizations to the custom Lists > Employees permission. For more
information, see Creating Custom Advanced Employee Permissions.
This feature includes the following permissions: Employee Self, Employee Public, Employee Confidential,
Employee Compensation, Employee System Access, and Employee Administration.
■ Employee Self — Employees with this permission have access to relevant information about
themselves on their employee record. This information can also be accessed by employees using their
Employee Center role by clicking My Profile under My Information. For details, see Employee Self
Permission Overview.
■ Employee Public — Employees with this permission have access to basic employee information, such
as job title. For details, see Employee Public Permission Overview.
■ Employee Confidential — Employees with this permission have access to a set of fields and sublists,
such as the Billing Class field, and the Time-Off subtab. For details, see Employee Confidential
Permission Overview.
■ Employee Compensation — Employees with this permission have access to compensation
information, such as base wage, and base wage type. For details, see Employee Compensation
Permission Overview.
■ Employee Administration — This permission is not automatically assigned to any roles. For details,
see Employee Administration Permission Overview.
■ Employee System Access — This permission is not automatically assigned to any roles. For details,
see Employee System Access Permission Overview.
With this feature, you can create custom employee permissions to include all or a set of standard fields
and sublists from the employee record. You can also add custom fields and sublists to custom employee
permissions. For more information, see Creating Custom Advanced Employee Permissions.
Note: Inline editing is available only with the Lists > Employees permission at access level Edit or
higher.
Note: When Advanced Employee Permissions is enabled, users who have access to effective
dating logs will only see what they are permitted to see based on the permissions and restrictions
assigned to their role. For example, roles with the Employee Confidential permission restricted to
subordinates see effective dating logs only for their direct reports and below. For details, see the
help topic Effective Dating for Employee Information.
View Advanced Employee Permissions Feature: Part 2 — Creating Custom Advanced Employee
Permissions
View Advanced Employee Permissions Feature: Part 3 — Customizing a Role Using Advanced
Employee Permissions
View Advanced Employee Permissions Feature: Part 4 — Using Advanced Employee Permissions
■ If you change the access level of the Employee Self permission to level Edit, be aware that this
will give employees the ability to make changes to the fields exposed with this permission,
which includes their compensation information. It is recommended that you use the default
access level View; however, if required, you can create a custom permission. For more
information, see Creating Custom Advanced Employee Permissions.
■ If you change the access level of the Employee Public, Employee Confidential, Employee
Compensation, and Employee Administration permissions to level Edit, be aware that this will
give users the ability to also create employees in NetSuite.
■ The standard NetSuite Lists > Employees permission gives access to all the information on
the employee record. This permission is intended for Human Resources Business Partners,
Chief People Officers (CPO), and Human Resources Directors. To restrict these roles to see
only employee administration information, remove the Lists > Employees permission, and add
the Employee Administration permission. For details, see Employee Administration Permission
Overview.
Retail Clerk (Web Services Only) ■ Employee Public — View/Active and Non-Terminated
■ Employee Record —Full
■ Employees — View
Note: Users are not able to view or edit future or past dated changes to their employee
information when assigned with a role that has this permission.
Primary Information:
■ Employee ID
■ Mr./Ms
■ Name
■ Initials
■ Job
■ Supervisor
■ Image
■ Email
■ Phone
■ Office Phone
■ Mobile Phone
■ Home Phone
■ Fax
■ Address
Classification:
■ Subsidiary
■ Department
■ Class
■ Location
Address
■ Default Shipping
■ Home
■ Label
■ Address
Human Resources
■ Social Security
■ Birth Date
Job Information:
■ Job Description
Subordinates:
■ Image
■ Name
■ Job Title
■ Location
■ Department
■ Subsidiary
■ Contact Info
Education:
■ Level of Education
■ Degree
■ Date Conferred
Personal:
■ Marital Status
■ Ethnicity
■ Gender
Time-Off
Available Now:
■ Type
■ Available this Year
■ Used this Year
■ Scheduled this Year
■ Available Now
Balances:
■ Type
■ Carried Over
■ Accrued
■ Used
■ Expired Carryover
■ Balance
Compensation Tracking
■ Compensation Currency
Primary Information:
■ Employee ID
■ Name
■ Initials
■ Supervisor
■ Image
■ Email
■ Phone
■ Office Phone
■ Mobile Phone
■ Fax
Classification:
■ Subsidiary
■ Department
■ Class
■ Location
Subordinates
Primary Information:
■ Employee ID
■ Name
■ Initials
■ Supervisor
■ Job
■ Image
■ Email
■ Phone
■ Office Phone
■ Mobile Phone
■ Fax
Classification:
■ Subsidiary
■ Department
■ Class
■ Location
Human Resources
■ Job Information:
□ Type
□ Employee Status
□ Job Description
□ Sales Rep
□ Support Rep
□ Project Resource
□ Project Manager
□ Default Project Resource Role
□ Work Calendar
□ Labor Cost
□ Hourly Rate
□ Hire Date
□ Last Review Date
□ Next Review Date
■ Subordinates:
□ Image
□ Name
□ Job Title
□ Location
□ Department
□ Subsidiary
□ Contact Info
■ Education:
□ Level of Education
Time-Off
■ Time-Off Plan
■ Start Date for Time-Off Calculations
■ Available Now:
□ Type
□ Available this Year (HRS)
□ Used this Year (HRS)
□ Scheduled this Year (HRS)
□ Available Now (HRS)
■ Balances:
□ Type
□ Carried Over (HRS)
□ Accrued (HRS)
□ Used (HRS)
□ Expired Carryover (HRS)
□ Balance (HRS)
Time Tracking
■ Time Approver
Commission
Compensation Tracking
■ Base Wage
■ Base Wage Type
Payroll
■ Compensation Type
The Base Wage, Base Wage Type, and Compensation Currency fields are associated with the
Compensation Tracking feature, and the Compensation Type field is part of SuitePeople US Payroll. For
details, see the help topics Tracking an Employee’s Compensation and Including an Employee in Payroll.
Note: The Employee System Access permission is not automatically assigned to standard roles
when the Advanced Employee Permission feature is enabled.
Primary Information:
■ Employee ID
■ Name
Access
■ Give Access
■ IP Address Restriction
■ Inherit IP Rules from Company
Roles:
■ Role
Global Permissions:
History:
■ Date/Time
■ User
■ Change
Note: The Employee Administration permission is not automatically assigned to standard roles
when the Advanced Employee Permissions feature is enabled.
Primary Information:
■ Employee ID
■ Initials
■ Supervisor
■ Mr/Ms
■ Job
■ Image
■ Name
■ Email
■ Mobile Phone
■ Address
■ Phone
■ Home Phone
■ Office Phone
■ Fax
Classification:
■ Subsidiary
■ Class
■ Location
Address
■ Default Shipping
■ Home
■ Label
■ Address
■ Edit
Human Resources
■ Birth Date
■ Job Information:
□ Type
□ Termination/Release Date
□ Employee Status
□ Job Description
□ Work Calendar
□ Hire Date
□ Last Review Date
□ Next Review Date
□ Expense and Purchasing:
▬ Expense Limit
▬ Expense Approver
▬ Expense Approval Limit
▬ Purchase Limit
▬ Purchase Approver
▬ Purchase Approval Limit
▬ Account
▬ Default Account for Corporate Card Expenses
□ Subordinates:
▬ Image
▬ Name
▬ Job Title
▬ Location
▬ Department
▬ Subsidiary
▬ Contact Info
□ Education:
Note: These examples use the default advanced employee permissions, but you can customize
these permissions. For details, see Creating Custom Advanced Employee Permissions and Setting
Employee Access for Advanced Employee Permissions.
The Lists > Employee Record, Lists > Perform Search, and Lists > Employees permissions are
standard NetSuite permissions, and are not part of Advanced Employee Permissions. However,
these permissions are required to use Advanced Employee Permissions. For more information
about the standard permissions, see the help topic NetSuite Permissions Overview.
Lists > Employee Edit — Access employee menus, for example List >
Record* Employees.
Employee Public View Active and Non- View and search basic employee information,
Terminated such as email address and supervisor, for all
active, non-terminated employees.
Employee Self View Own Only View relevant information about themselves on
their employee record, such as job description
and compensation.
The Lists > Employee Record and Lists > Perform Search permissions are standard NetSuite permissions,
and are not part of Advanced Employee Permissions. However, these permissions are required to use
Advanced Employee Permissions. For more information about the standard permissions, see the help
topic NetSuite Permissions Overview.
Lists > Employee View — Access employee menus, for example List >
Record* Employees.
Employee Public View Active and Non- View and search basic employee information,
Terminated such as email address and supervisor, for all
active, non-terminated employees.
Employee Self View Own Only View relevant information about themselves on
their employee record, such as job description
and address.
The Lists > Employee Record and Lists > Perform Search permissions are standard NetSuite permissions,
and are not part of Advanced Employee Permissions. However, these permissions are required to use
Advanced Employee Permissions. For more information about the standard permissions, see the help
topic NetSuite Permissions Overview.
Lists> Employee Full — Access employee menus, for example List > Employees.
Record*
Employee Full Inherit from Role View, create, edit, and search for personal information,
Administration such as home phone and marital status, for employees
who match the restrictions defined on the Role page. If
no restrictions are defined, this information is available
for all employees.
Employee View Subordinates View compensation information for direct reports and
Compensation below.
Employee Public View Active and Non- View and search basic employee information, such
Terminated as email address and supervisor, for all active, non-
terminated employees.
The Lists > Employee Record and Lists > Perform Search permissions are standard NetSuite permissions,
and are not part of Advanced Employee Permissions. However, these permissions are required to use
Advanced Employee Permissions. For more information about the standard permissions, see the help
topic NetSuite Permissions Overview.
Lists > Employee Full — Access employee menus, for example List > Employees.
Record*
Lists > Employees* Full — View, edit, and create employee record information for all
employees who match the restrictions defined on the Role
page. For example, if a location restriction is set, access is
only for the employees in the set location or sublocation.
If no restrictions are defined, access is given to all the
information on the employee record for every employee.
Employee Public View Active and Non- View and search basic employee information, such as email
Terminated address and supervisor, for all active, non-terminated
employees.
The Lists > Employee Record, Lists > Perform Search, and Lists > Employees permissions are standard
NetSuite permissions, and are not part of Advanced Employee Permissions. However, these permissions
are required to use Advanced Employee Permissions. For more information about the standard
permissions, see the help topic NetSuite Permissions Overview.
Lists > Employee View — Access employee menus, for example List >
Record* Employees.
Employee System Full Inherit from Role Give access and assign roles to employees who
Access match the restrictions defined on the Role page.
Employee Public View Active and Non- View and search basic employee information, such
Terminated as email address and supervisor, for all active, non-
terminated employees.
The Lists > Employee Record and Lists > Perform Search permissions are standard NetSuite permissions,
and are not part of Advanced Employee Permissions. However, these permissions are required to use
Advanced Employee Permissions. For more information about the standard permissions, see the help
topic NetSuite Permissions Overview.
■ Employees — This permission is intended for HR Business Partners, CPOs, and HR Directors.
Users assigned to a role with this permission have access to all information on the employee
record.
Note: When you select a permission, the default access level and restrictions are
automatically selected, but you can change these.
5. If required, change the default access level for the selected restriction from the Level list. For
details, see the help topic Access Levels for Permissions.
Note: When two employee permissions are included with a role, one at level view and
another at level edit, users assigned to the role see a combination of the fields and sublists
they are permitted to view on the employee record. In edit mode, only the fields and
sublists that the user can edit are visible on the employee record.
■ If you change the access level of the Employee Self permission to level Edit, be aware
that this will give employees the ability to make changes to the fields exposed with
this permission, which includes their compensation information. It is recommended
that you use the default access level View; however, if required, you can create a
custom permission. For more information, see Creating Custom Advanced Employee
Permissions.
■ If you change the access level of the Employee Public, Employee Confidential, Employee
Compensation, and Employee Administration permissions to level Edit, be aware
that this will give users the ability to also create employees in NetSuite. For more
information, see the help topic Access Levels for Permissions.
■ The standard NetSuite Lists > Employees permission gives access to all the information
on the employee record. This permission is intended for Human Resources Business
Partners, Chief People Officers (CPO), and Human Resources Directors. To restrict these
roles to see only employee administration information, remove the Lists > Employees
permission, and add the Employee Administration permission. For details, see Employee
Administration Permission Overview.
6. If required, change the default restriction for the selected restriction from the Restrictions list.
Choose from the following:
■ Inherit from Role — Select this when you want the permission to inherit the restrictions set on
the Role page. For more information about setting restrictions on the Role page, see the help
topic Customizing or Creating NetSuite Roles.
■ Subordinates — Select this when you want the permission to be restricted by subordinates.
For example, you could add this restriction to the Employee Confidential permission, so that
users assigned to this role would have access to public and confidential employee information
only for their subordinates.
■ Active and Non-Terminated — Select this when you want the permission to be restricted
to active and non-terminated employees. For example, you could add this restriction to the
Employee Public permission, so that users assigned to this role would have access to basic
employee information for all active and non-terminated employees only.
■ Own Only — Select this when you want to restrict the permission to own only. This means,
users assigned to this role have access to the fields and sublists exposed with the permission
for only themselves. For example, you could add this restriction to the Employee Self
permission, so that users assigned to this role would only have access to basic personal
employee information for themselves.
7. Click Add.
8. Repeat these steps for each permission you want to assign to the role.
Note: If you assign an additional role to a user who is currently logged in to NetSuite, that
user must log out and log back in to see the newly assigned role. The same is true if you add
permissions to an existing role while a user is currently logged in to NetSuite. The user needs to
log out and log back in to exercise the new permissions.
You have two choices when creating custom advanced employee permissions. You can create a new
permission using a custom set of fields and sublists from the employee record. You can also customize
a standard employee permission to only include a subset of the fields and sublists that are exposed, or
customize it to include additional fields and sublists.
Standard employee permissions cannot be modified, so it is recommended that you use these
permissions as templates to create your own custom employee permissions.
■ By default, when the Advanced Employee Permissions feature is enabled, any customization’s
created with NetSuite SuiteBuilder that are included with the standard Lists > Employees
permission are preserved. However, customization’s are not preserved when the Lists >
Employees permission is customized. If required, customization’s need to be manually added
to the custom Lists > Employees permission.
■ Both inline editing and inactivating employees from the Employees List page are disabled for
users assigned to a role that has a custom employee permission.
■ Before deploying client or server side scripts that gain access to employee information make
sure:
□ The employee field or sublist is available to the role.
□ The role has the correct employee permission to see the employee field or sublist for the
types of employees being viewed or edited.
□ Some scripts (including third-party scripts) may fail if they attempt to access parts of the
employee record that they are not permitted to access, with the role and permissions they
are assigned.
For more information, see Before Enabling the Advanced Employee Permissions Feature.
2. From the Manage Permissions page, you can either create a custom or new employee permission.
a. To create a custom employee permission, click Customize beside the employee permission
you want to customize. All of the standard fields and sublists associated with the parent
permission are inherited. You can make changes as necessary.
b. To create a new employee permission that does not start with a list of associated fields and
sublists, select New Permission from the Manage Permissions page.
3. If required, you can add standard and custom fields to the permission. For more information, see
Adding Standard Fields and Sublists to Advanced Employee Permissions and Creating Custom
Fields for Advanced Employee Permissions.
4. To finish, click Save.
To remove the permission, click Actions > Delete. When the permission is assigned to a role you will
need to remove it from the role before it can be deleted.
Related Topics
10. Repeat these steps for each field and sublist that you want to include.
11. To finish, click Save.
Alternatively, click +Insert, select the employee record and field, and click Add. To remove a field, select it
from the list, and click Remove.
Related Topics
Note: The Show In List box on the custom entity field record is not supported with Advanced
Employee Permissions. This means that custom fields are not shown on the Employees List page
when this box is checked. To display custom fields with Advanced Employee Permissions, you need
to create a custom view that contains the custom fields. To do this, click the Edit View button from
the Employees List page and manually add the custom fields.
Related Topics
Important: Permission access levels are set on the Role page, when the advanced employee
permission is assigned to the role and not on the custom entity record. For example, if a
permission is assigned to a role at access level View, any custom fields that are added to the
permission respect that access level.
1. To create a custom sublist, go to Customization > Forms > Sublists > New.
2. In the Type field, select Entity.
3. Check the Employee box.
4. In the Search field, select the saved search that returns the results you want to appear on the
record. If the saved search does not appear in the list, check the saved search settings. The first
item listed on the Available Filters subtab must be a List/Record type. Otherwise the saved search
is not available to assign as a sublist. For more information, see the help topic Saved Searches for
Custom Sublists.
5. In the Label field, enter a label for this sublist.
6. In the Tab field, select the subtab where you want the sublist to appear.
7. Repeat these steps for each custom sublist you want to create.
8. To finish, click Save. The custom sublist you created automatically appears in the Custom Sublists
subtab on the Permission page.
Related Topics
9. Click Add. Alternatively, click +Insert, select the record type and sublist, and click Add
10. Repeat these steps for each custom sublist and field you want to add to the permission.
11. To finish, click Save.
Related Topics