SuiteApprovals 2026.2.2 Script Role and Permissions

SuiteApprovals 2026.2.2 adds SAS - Script Executor, revises user permissions, and requires a customized role and deployment updates for ECO approvals.

·5 min read·17 views·NetSuite 2026.2·View Oracle Docs

SuiteApprovals SuiteApp version 2026.2.2 introduces SAS - Script Executor for specified script deployments that previously ran with Administrator privileges. It also revises user permission requirements. Engineering Change Order approvals require a customized execution role and deployment updates after production upgrade; the SuiteApp version is currently available only to a limited number of accounts.

Availability: Contact NetSuite Customer Support for information about version 2026.2.2 availability. Plan the checks below around the SuiteApp update rather than assuming availability from a platform release number.

What Changes With SAS - Script Executor?

Previously, SuiteApprovals scripts ran with Administrator privileges. The new dedicated role supplies only the permissions needed to perform SuiteApprovals functions.

The SuiteApp locks and manages SAS - Script Executor. It is intended only for SuiteApprovals script execution and must not be assigned to employee records. Assigning it to an approver is therefore not the way to meet the updated user-role requirements.

Treat script execution and employee permissions as separate review items. The deployment changes determine the execution role for the listed scripts; the user-permission changes below establish the access required for submission, resubmission, approval, and rejection.

Which Script Deployments Change?

The SuiteApp sets both the execution role and the audience role for five deployments. The email approval processing deployment receives only the execution-role change.

Script deploymentExecute as Role fieldInternal Roles field on Audiences subtab
SAS Approval List SUSAS - Script ExecutorSAS - Script Executor selected
SAS Approval Rule SUSAS - Script ExecutorSAS - Script Executor selected
SAS Approval Rule List SUSAS - Script ExecutorSAS - Script Executor selected
SAS Approval Rule AssistantSAS - Script ExecutorSAS - Script Executor selected
SAS Supported Records SUSAS - Script ExecutorSAS - Script Executor selected
SAS Email Approval Processing SUSAS - Script ExecutorUnchanged

When reviewing deployments, preserve this distinction. An unchanged Internal Roles field on SAS Email Approval Processing SU matches the documented update; it is not, by itself, evidence that the update is incomplete. The other five deployments receive the new role in both fields.

What Must ECO Approval Teams Do After Upgrade?

The supplied SAS - Script Executor role does not include the permissions required to process Engineering Change Order (ECO) records. Until the required changes are completed, users cannot approve or reject ECO records through SuiteApprovals.

After your production account is upgraded:

  1. Create a customized copy of SAS - Script Executor.
  2. Add the required ECO permissions to that copy.
  3. Update the affected script deployments before processing ECO records.

The release note does not enumerate the ECO permissions or identify the deployment-by-deployment changes. Follow Oracle's Updating SuiteApprovals Script Deployments for Engineering Change Order Approvals procedure for implementation details rather than guessing the permission set.

As a validation step, test approval and rejection with the intended ECO approver after completing the configuration. Keep that test separate from the required setup: ECO approvers also need the Custom Record Types access described below.

How Do User Approval Permissions Change?

Review user roles alongside script deployments. Completing the execution-role configuration does not replace the stated requirements for individual approvers.

Action or user groupUpdated requirementPrevious requirement or qualification
Transaction approval or rejectionAt least Edit for each transaction typeEligible approvers previously needed View; the Employee Center vendor bill exception is below
Employee Center vendor bill approval or rejectionBills set to View and Vendor Bill Approval set to EditExisting SuiteApprovals permissions and record and subsidiary access requirements still apply
Standard and customized Employee Center rolesAccess to the SAS Supported Record Permissions SU script deployment audienceRequired for both standard and customized roles
ECO and Email Approval Log approversAt least View for Custom Record TypesAdditional approver permission requirement
Submit for Approval and ResubmitAt least Create for each supported transaction typePreviously required at least Edit

Keep the deployment names distinct: SAS Supported Record Permissions SU is the audience requirement for Employee Center roles. SAS Supported Records SU is one of the deployments receiving the new execution role.

For testing, separate submission from approval. Meeting the Create threshold for submission does not establish that a role meets the Edit threshold for approval. Test Employee Center vendor bills separately because their stated permission combination differs from the general transaction-approver requirement.

What Should Administrators Verify?

Use the documented changes to build a validation checklist for the approval paths your account uses:

  • Confirm SuiteApp version availability with NetSuite Customer Support.
  • Inspect the six deployment configurations, including the email deployment's unchanged audience field.
  • Review approval and rejection permissions for each relevant transaction type.
  • Check the specified vendor bill permissions and deployment-audience access for standard and customized Employee Center roles.
  • Complete the ECO role-copy and deployment work before processing ECO records.
  • Test submission, resubmission, approval, rejection, and email approval paths where applicable.

For a separate review of the document-review interface, see SuiteApprovals portlet behavior. Teams handling vendor bill intake can also review Bill Capture intake and review while keeping intake checks distinct from the approval permissions described here.

Who This Affects

  • Administrators and script deployment maintainers: Review execution roles, deployment audiences, and the ECO configuration exception.
  • Transaction approvers: Check access for each transaction type they approve or reject, rather than relying on the previous View threshold.
  • Employees submitting transactions: Review the reduced permission threshold for Submit for Approval and Resubmit.
  • Employee Center users: Check both the vendor bill permission combination and the script deployment audience requirement.
  • ECO and Email Approval Log approvers: Check Custom Record Types access. ECO processing also requires the customized execution role and deployment updates.

Key Takeaways

  • SuiteApprovals 2026.2.2 has limited availability; contact NetSuite Customer Support for availability information.
  • SAS - Script Executor replaces Administrator execution privileges on specified deployments and must not be assigned to employee records.
  • ECO approvals require a customized role and deployment updates after production upgrade.
  • Transaction approval generally requires at least Edit; submission and resubmission require at least Create.
  • Employee Center vendor bill approvals have a specific permission exception, plus an audience-access requirement.

Frequently Asked Questions (4)

Can I assign SAS - Script Executor to an approver to satisfy the updated approval permissions?
No. SAS - Script Executor is locked and managed by the SuiteApp, is intended only for SuiteApprovals script execution, and must not be assigned to employee records. Review script execution roles separately from individual user permissions.
Which SuiteApprovals deployments need SAS - Script Executor in both the execution role and audience fields?
SAS Approval List SU, SAS Approval Rule SU, SAS Approval Rule List SU, SAS Approval Rule Assistant, and SAS Supported Records SU need SAS - Script Executor in both fields. SAS Email Approval Processing SU receives the execution-role change only; its Internal Roles audience field remains unchanged.
What must we configure before approving or rejecting Engineering Change Orders after the production upgrade?
Create a customized copy of SAS - Script Executor, add the required ECO permissions, and update the affected script deployments before processing ECO records. The supplied role lacks the permissions needed for ECO records, and ECO approvers also need at least View access for Custom Record Types. Follow Oracle’s ECO deployment procedure for the specific permissions and deployment changes.
What permissions do users need to submit transactions versus approve them in SuiteApprovals 2026.2.2?
Submitting or resubmitting requires at least Create for each supported transaction type, while transaction approval or rejection generally requires at least Edit for each transaction type. Employee Center vendor bill approval or rejection is a separate case: Bills must be set to View and Vendor Bill Approval to Edit. Existing SuiteApprovals permissions and record and subsidiary access requirements still apply.

Weekly Update History (1)

Accounting SuiteAppsadded

Added entry for SuiteApprovals Enhancements.

View Oracle Docs
Source: SuiteApprovals Enhancements — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Accounting

View all Accounting articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →