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!
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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Bundle Permissions for public bundle
I am currently writing a bundle that can be used by any Netsuite developer. It contains two core features that can be used independent from each other. Currently I am struggling to find the best practices for bundle developers to offer the client that installs the bundle to configure and change the permissions of the different bundle features and pages according to there own permission and role model. What is the best practice for that?
Currently the main suggestion I've heard is to allow them to change the deployment of my records to adjust permissions but I was wondering if that is really the way to go or if there are any other options?
0