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.
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 deployment | Execute as Role field | Internal Roles field on Audiences subtab |
|---|---|---|
| SAS Approval List SU | SAS - Script Executor | SAS - Script Executor selected |
| SAS Approval Rule SU | SAS - Script Executor | SAS - Script Executor selected |
| SAS Approval Rule List SU | SAS - Script Executor | SAS - Script Executor selected |
| SAS Approval Rule Assistant | SAS - Script Executor | SAS - Script Executor selected |
| SAS Supported Records SU | SAS - Script Executor | SAS - Script Executor selected |
| SAS Email Approval Processing SU | SAS - Script Executor | Unchanged |
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:
- Create a customized copy of SAS - Script Executor.
- Add the required ECO permissions to that copy.
- 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 group | Updated requirement | Previous requirement or qualification |
|---|---|---|
| Transaction approval or rejection | At least Edit for each transaction type | Eligible approvers previously needed View; the Employee Center vendor bill exception is below |
| Employee Center vendor bill approval or rejection | Bills set to View and Vendor Bill Approval set to Edit | Existing SuiteApprovals permissions and record and subsidiary access requirements still apply |
| Standard and customized Employee Center roles | Access to the SAS Supported Record Permissions SU script deployment audience | Required for both standard and customized roles |
| ECO and Email Approval Log approvers | At least View for Custom Record Types | Additional approver permission requirement |
| Submit for Approval and Resubmit | At least Create for each supported transaction type | Previously 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?
Which SuiteApprovals deployments need SAS - Script Executor in both the execution role and audience fields?
What must we configure before approving or rejecting Engineering Change Orders after the production upgrade?
What permissions do users need to submit transactions versus approve them in SuiteApprovals 2026.2.2?
Weekly Update History (1)
Was this article helpful?
More in Accounting
- System Notes v2 Workbook for Promotion Code Tracking in NetSuite
System Notes v2 Workbook tracks changes to promotion codes and coupons, enhancing auditing and management capabilities in NetSuite 2025.2.
- Journal Line Sublists Standardized for NetSuite 2026.1
With NetSuite 2026.1, journal line sublists are standardized to keyed configurations, allowing precise line updates and enhancing financial accuracy.
- Email Notification Matrix for Workflow Approvals
The Email Notification Matrix outlines who receives notifications at each workflow stage, streamlining approval processes.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
Also from NetSuite 2026.2
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- NetSuite Next: Readiness, Preview, and Ask Oracle
Eligible administrators can request a NetSuite Next preview, set up Ask Oracle, and prepare data, roles, customizations, and navigation.
Advertising
Reach Accounting Professionals
Put your product in front of NetSuite experts who work with Accounting every day.
Sponsor This Category