Ask your NetSuite Admin to enable User Access Tokens for your role as this can greatly reduce NetSuite concurrency issues. Click here to send them an email request or share this article with them.
Step 1: Go to Setup > Users/Roles > Manage Roles
Step 2: Look for the role name that you wish to edit
Step 3: Go to Permissions > Setup and make sure you have User Access Tokens and SOAP Web Services set to FULL.
More detail
NetSuite recommends that users connect to NetSuite with tokens when using applications such as CloudExtend and has provided a means to generate these tokens automatically. during the login flow. Once a user enters their user name and password CloudExtend will attempt to create a token pair for future logins. If the end-user does not have the proper permissions this process will fail and the user will need to click the back button and select basic login.
For the login flow to be able to generate tokens on behalf of the user ensure that their roles have the User Access Tokens permission. When a role has this permission the NetSuite login flow will automatically generate tokens on your behalf and log you in with token-based authentication which can greatly reduce NetSuite concurrency issues.
Role-Specific Limitations with Tokens
Specialized NetSuite roles, such as CRM-specific roles, often have preset limitations that restrict the addition of new permissions. For example, the “Custom specialized user: CRM” role cannot include permissions like User Access Tokens and SOAP Web Services required for CloudExtend. To resolve this issue, consider assigning a role that permits adding required permissions, or clone a standard NetSuite role, add the necessary permissions, and reassign it.
Users without this permission will see an error when logging in You cannot continue this authorization flow. Your current role has insufficient permission. Please contact your account administrator. and will need to click the back button and log in with basic credentials.
Addressing Role-Specific Permission Limitations
Ensure that roles like specialized CRM roles do not restrict essential permissions for CloudExtend. Assigning a different role or creating a custom role may resolve these issues. After updating roles, ask affected users to log out and log back into CloudExtend to apply the changes.