Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!

Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!

Check out this thread to learn more!

Restrict class by ROLE (vs. user)

edited Dec 2, 2019 5:49PM in SuiteCloud / Customization

Goal: Restrict user access by classification based on the role they are using.

The classification setting is set on a given user. I have a need for a given user to be able to set a transaction level class, but want to leverage the restrictions as described here:
https://system.na1.netsuite.com/app/...opic=EDIT_ROLE
under each role.

Example: User has 2 roles available. Each role should force transactions to have a given class. Using the Restricting Accounts for Roles recommendation and Employee Restrictions and Class Restrictions I can restrict a user's access to 1 class only as the class setting is on the USER. So, in my implementation, I created 2 roles. One role is setup as described and successfully restricts a user's behavior such that all trans have the correct class. The second role is setup by naming convention to be the 2nd class, but in reality the users can select either class. Thus in that situation, the user is able to set the wrong class on a given transaction.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 3 (Jul-Sep 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders