NetAsset - Unable to Access System Setup

Overview

If you are locked out of the NetAsset System Setup page and unable to update Suitelet permissions, even when assigned the Administrator or NetAsset Administrator role, there is a workaround that allows you to regain access. This process involves navigating directly to the Suitelet deployment record for the global settings, updating its permissions, and then returning to System Setup to proceed with updates as normal.



Key Assumptions

  • You already have either the Administrator or NetAsset Administrator role assigned.

  • The lockout issue is due to missing permissions on the Suitelet deployment rather than an account or role deactivation.

  • Access to Customization > Scripting > Script Deployments in NetSuite.


Step-by-Step Process

  1. Navigate to Script Deployments
    Go to: Customization > Scripting > Script Deployments

  2. Filter for Suitelet Type

    • Open the filter options.

    • Set Type to Suitelet.

  3. Locate the NetAsset Global Settings Suitelet

    • Look for the deployment named NetAsset Setup SL (or similar name matching your configuration).

    • Click View to open the record.

  4. Edit Permissions

    • While still on the deployment record, click Edit.

    • Add the Administrator and NetAsset Administrator roles to the permissions list.

    • Click Save.

  5. Test Access

    • Navigate to NetAsset>NetAsset Setup>System Setup to confirm access is restored.

  6. Proceed with Updates

    • Once in System Setup, update Suitelets as needed.

    • You may also use the Update All Suitelets option if available in your environment.


Limitations / Things to Be Aware Of

  • This workaround assumes you can still access Script Deployments in Customization. If you cannot, you will need another administrator to follow this process for you.

  • Be careful when editing deployment permissions — removing necessary roles can cause lockouts for other users.


Troubleshooting

  • Still receiving the permissions error after updating roles?

    • Double-check that the correct Suitelet deployment was modified.

    • Ensure your session is active — log out and log back in before retrying.

  • Cannot find the deployment?

    • Expand your filters to search across all script deployments, then use the search bar to locate NetAsset-related records.


Was this article helpful?