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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
NetSuite Global Login Table
To log in, it does not seem reasonable that NetSuite would look into every account, for Employees, Partners, and Customers for an ID to match.
-- many tables to search (at least 3 in each account)
-- when any account adds a record, all other accounts would need to be searched for a duplicate (and the first created would have to be marked as the real one since the record is created with a warning message that it is not going to be used for login)
More reasonable is that NetSuite copies this information when the records are created/updated to a Global Login Table (id, password, account, role).
0