Week 5 of 8
Roles, permissions and 2FA
If your testers use the Administrator role, every permission defect passes. The A/P clerk who suddenly cannot pay bills, or the warehouse user who can now edit prices, only show up when you test as them.
NetSuite requires two-factor authentication for Administrator and other highly privileged roles in every account type, including sandbox and Release Preview, and API access by those roles cannot use user credentials. Login and authentication belong in every regression cycle.
This week: test as the role, and compare roles before and after
- Create one test user per customized role, holding only that role, and use it for every workflow test.
- Write a negative test for each role as well: what it must not be able to do, such as an A/P clerk changing vendor bank details.
- Before and after each upgrade, run Setup > Users/Roles > Show Role Differences and export it. Any unexpected difference is a defect until explained.
- List your segregation-of-duties conflicts and check that no single role holds both sides without a control.
Number of the week
100
roles is the most Oracle advises comparing at once in Show Role Differences. Small teams rarely need more.
Source: Oracle NetSuite Help Center, Showing Role Permission DifferencesUse this week
- NetSuite Role & Permission Test Matrix →
Positive and negative tests per role, SoD conflicts and a release diff log.
- UAT Sign-Off Form (Word) →
Record that each process owner tested with their own role.
Next week: integrations, and the 2027 and 2028 authentication deadlines that come with them.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.