megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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!

Custom Role - Employee Restrictions

in CRM 7 comments

What is the functional difference between "none - no default" and "none - default to own"? I've read the help docs that describe the latter as "There is no restriction on what can be selected. Record access is not determined by this field. Fields of this type will select the user by default."

What are "fields of this type"? Can someone provide an example to illustrate the difference? I know I don't want any restrictions on the role I'm creating. I'm wondering if there's any benefit to the default to own setting that my users will see.

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 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders