A Cause of Confusion

Script Permissions. A source for great confusion. A place where what is visible to some is not visible to others. This tip will try to help us all understand and use this powerful feature in a responsible way, where script permissions help our companies rather than complicate them.

How Script Permissions Work

There are three places where a script exists in NetSuite. The File Cabinet, Scripts, and Script Deployments. Script permissions are always and only adjusted on the script deployment. Keep in mind that you may need Administrator access to view the script deployments.

Script permissions are not always especially intuitive. The best rule of thumb is just finding what works along certain important guidelines. Here are two crucial things to know about script permissions:

  1. The “Status” field (highlighted in smaller upper box) specifies whether a script is in testing or is released. “Testing” means that the script will only run for the user that created or owns the script. “Released” means that the script is normal. “Normal,” however, won’t be viewable if no “Roles” are selected in the lower highlighted section.
  2. The “Audience” sub-tab specifies who will see the released script. At SuiteRep, we almost always just click the “Select All” checkbox to make sure everyone sees the deployed script. This is usually all that’s needed. If you’re feeling stingy you can venture into selecting only certain groups or employees, although this is not typically necessary.

Problematic Scenarios

In this NetSuite tip, we will give three scenarios where you may find yourself needing to adjust script permissions. After discussing each scenario, we will then look into the possible solutions available to you.

First Scenario: The Mistaken Developer

If you have worked with SuiteScript developers in the past, you may have experienced this common scenario. Developers typically like to keep their scripts in “testing” mode until they are 100% certain that the script is safe to release. One of the benefits of the “testing” permission is that it allows developers to experience the script while the rest of the company is protected from using it. This can be a time saver if there are bugs in the script, but it can also be a source of frustration if the developer forgets to release the script publicly.

The good news is that this is an easy fix, with two options. Anyone with Administrator access can quickly edit the script deployment and release it to all roles. Be sure to verify that the script is ready for production, however, before releasing a script on your own. You should also be able to send your developer a quick message, and he can easily modify the script permissions for you.

Second Scenario: The Broken Script

From time to time as NetSuite evolves, scripts sometimes stop working like they used to. Often what’s needed is a quick modification in the code, but not everyone reads code as their native language. In an emergency, do you know how to change a script back to “testing” on the fly until help is on the way?

The first thing you should do is contact a developer, preferably someone who created the script or is familiar with your company processes. If for some reason you are looking for someone else to help out, we at SuiteRep would be happy to help in any way we can. After contacting someone for help, you may want to move the problematic script back to Testing if it is preventing your team from performing important tasks.

Third Scenario: Shifted Requirements

In certain situations, a script can be release to only a few members of a team who actively use the script. But as our teams change over the years, the script will need to follow that change. Is there an easy way to change who can access the script?

At SuiteRep, we typically make the scripts deployed to all “Roles” unless requested otherwise. This would prevent confusion over rotating teammates in the company. If it is necessary to have the script viewable by only a select few employees, an Administrator can easily adjust the specific employees in the script deployment (under the “Audience” sub-tab) as needed.

Conclusion

We hope you find this NetSuite tip helpful. If you have any questions about script permissions or anything else NetSuite related, don’t hesitate to reach out to us! We would love to help your company in any way we can.