SuiteApprovals 2026.2.2 Role and Permission Changes: Admin Checklist
Validate SuiteApprovals 2026.2.2 script execution roles, transaction approval permissions, and Employee Center access. Identify the separate ECO configuration work required before processing approvals.
SuiteApprovals 2026.2.2 role and permission changes require two separate administrator reviews: script execution settings and employee approval permissions. The update introduces SAS - Script Executor, changes transaction permission thresholds, and requires additional configuration for Engineering Change Order (ECO) approvals. Plan validation around your account’s SuiteApp update, not simply the NetSuite platform release.
Key takeaways
- Confirm version 2026.2.2 availability with NetSuite Customer Support; availability is limited.
- Five deployments receive SAS - Script Executor in both execution-role and audience settings. SAS Email Approval Processing SU receives only the execution-role change.
- Never assign SAS - Script Executor to employee records.
- Transaction approval and rejection generally require at least Edit; Submit for Approval and Resubmit require at least Create.
- Employee Center vendor bills have a specific permission combination and a separate deployment-audience requirement.
- ECO approvals require a customized execution role and deployment updates after the production upgrade. Approver permissions alone do not complete that setup.
1. Confirm SuiteApprovals 2026.2.2 availability
The SuiteApprovals SuiteApp version is the relevant checkpoint. Version 2026.2.2 is available only to a limited number of accounts; the 2026.2 platform release label does not establish that your account has received this SuiteApp update. The release-note entry for SuiteApprovals Enhancements was added on 2026-11-16, but that date is not universal account availability.
Before scheduling validation:
- Contact NetSuite Customer Support about version 2026.2.2 availability. Plan the review around the SuiteApp update applicable to your account.
- Separate execution-role checks from user-permission checks. Record deployment settings independently from employee and approver role requirements. Passing one review does not satisfy the other.
- Identify the approval paths in scope. Include submission, resubmission, approval, rejection, Employee Center vendor bills, email approvals, and ECO approvals wherever your account uses them.
For each test, record the action, transaction type, user role, expected permission threshold, and result. This recommended test record helps distinguish a deployment review from a successful approval test rather than treating either as evidence that every path works.
2. Validate the six script deployments
Previously, SuiteApprovals scripts ran with Administrator privileges. The new dedicated role supplies the permissions needed to perform SuiteApprovals functions. The SuiteApp locks and manages SAS - Script Executor, and it must not be assigned to employee records. Giving it to an approver is not a remedy for an approval-permission failure.
The update does not apply an identical audience change to all six deployments. Compare both fields with the documented configuration:
| 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 |
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.
Record the two fields separately during review. A single “new role present” checkbox would miss the distinction between execution context and audience configuration.
ECO exception: This table describes the general update, not the complete ECO configuration. Accounts processing ECO records must also complete the customized-role and deployment work in section 5. Do not use this table as a substitute for Oracle’s ECO-specific procedure.
3. Review submission and approval permissions separately
The revised thresholds move submission and approval in different directions. Submit for Approval and Resubmit previously required at least Edit and now require at least Create for each supported transaction type. Transaction approval and rejection generally move from the previous View threshold for eligible approvers to at least Edit for each transaction type.
| 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; Employee Center vendor bills are a separate case |
| Submit for Approval and Resubmit | At least Create for each supported transaction type | Previously required at least Edit |
| ECO and Email Approval Log approvers | At least View for Custom Record Types | Additional approver permission requirement |
For example, a successful submission under a role with Create does not establish that the role can approve or reject the same transaction type. Likewise, a deployment using the expected execution role does not establish that the employee has the required approval access.
Use three separate checks:
- Submission roles: Review the Create threshold for each supported transaction type employees submit or resubmit.
- Approver roles: Review the Edit threshold for each transaction type users approve or reject, subject to the Employee Center vendor bill exception below.
- ECO and Email Approval Log approvers: Check Custom Record Types at View or higher as an additional user-permission requirement.
Avoid treating one successful transaction test as coverage for every transaction type. The requirements are stated per type, so the validation record should identify which types were actually tested.
4. Check Employee Center vendor bills and audience access
Employee Center vendor bill approval and rejection use a specific permission combination rather than the general transaction-approver threshold:
- Bills: View.
- Vendor Bill Approval: Edit.
- Existing access: SuiteApprovals permissions and record and subsidiary access requirements still apply.
There is also a deployment-audience requirement for both standard and customized Employee Center roles. Check access to the SAS Supported Record Permissions SU script deployment audience.
Two similar deployment names must remain separate in the checklist:
| Deployment | What to review |
|---|---|
| SAS Supported Record Permissions SU | Audience access for standard and customized Employee Center roles |
| SAS Supported Records SU | Execution-role and audience changes shown in the six-deployment table |
Do not mark the Employee Center audience check complete merely because SAS Supported Records SU has the expected execution role. Those are different deployment entries with different checks.
Test vendor bill approval and rejection separately from general transaction approvals. Record the exact Employee Center role used, including whether it is standard or customized. If your account uses both, include both in the validation plan rather than assuming the result for one establishes access for the other.
5. Complete ECO configuration after the production upgrade
The supplied SAS - Script Executor role lacks the permissions needed to process ECO records. Until the required configuration is complete, 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.
Follow Oracle’s Updating SuiteApprovals Script Deployments for Engineering Change Order Approvals procedure for the permission set and deployment-specific implementation.
The release note supplies the required sequence but does not enumerate the ECO permissions or identify the deployment-by-deployment changes. Do not infer those details from the general six-deployment table or invent a permission recipe.
Keep setup and validation distinct. After completing the configuration, verify that the intended ECO approver has at least View for Custom Record Types, then test approval and rejection with that approver.
Neither assigning the supplied execution role to an employee nor granting the approver Custom Record Types access replaces the customized-role and deployment work. The first conflicts with the role’s stated purpose; the second addresses a separate user-permission requirement.
6. Test each approval path used in your account
Use separate results for separate actions. The goal is to connect each result to a user role, transaction type, and documented requirement—not simply to record that “SuiteApprovals works.”
| Test | Permission or configuration to validate |
|---|---|
| Submit for Approval | At least Create for each supported transaction type in scope |
| Resubmit | At least Create; record a separate result from initial submission |
| General transaction approval and rejection | At least Edit for each transaction type in scope |
| Employee Center vendor bill approval and rejection | Bills at View, Vendor Bill Approval at Edit, deployment-audience access, and existing access requirements |
| Applicable email approval paths | Relevant user permissions, including Custom Record Types at View or higher for Email Approval Log approvers |
| ECO approval and rejection | Completed customized-role and deployment work, plus the intended approver’s Custom Record Types access |
For email approval testing, retain the distinction between the deployment’s execution role and its unchanged audience field. For ECO testing, complete the required configuration before attempting to validate approval and rejection.
If a test fails, compare the result with the relevant checklist layer first: execution settings, deployment audience, user permissions, or ECO-specific setup. This gives the investigation a defined starting point without assuming every failure calls for broader employee access or changes to the supplied execution role.
FAQ
Can I assign SAS - Script Executor to an approver?
No. The SuiteApp locks and manages this role for script execution, and it must not be assigned to employee records. Review approver permissions separately.
Which deployment keeps its existing Internal Roles audience setting?
SAS Email Approval Processing SU receives the Execute as Role change to SAS - Script Executor, while its Internal Roles field remains unchanged.
Does Create permission let a user approve transactions?
Not by itself. At least Create meets the stated threshold for submission and resubmission. Transaction approval and rejection generally require at least Edit, with the separate Employee Center vendor bill combination described above.
Is Custom Record Types access enough to enable ECO approvals?
No. ECO approvers need at least View for Custom Record Types, but ECO processing also requires a customized copy of SAS - Script Executor, the required ECO permissions, and affected deployment updates.
Related reading
These articles address separate reviews; they do not replace the SuiteApprovals checks above:
Advertising
Reach Administration Professionals
Put your product in front of NetSuite experts who work with Administration every day.
Sponsor This Category