This is unbelievable. I can't believe the lack of security applied to NetSuite when it comes to permissions and roles. Here's a couple of examples:
1. Set up a saved search to lookup customers with specific fields set (to ensure that the user can only see customers with these fields set). Restrict the saved search for 'Customers' to the user's role.
Result: Run the saved search under the specified role and only the customer's you expect show in the list. HOWEVER, in the lower right is the 'Edit View' button to allow them to edit the view. In other words, you CANNOT prevent the user from editing a saved search! You can stop them from saving it under the same name but they can edit it, remove the criteria that prevents them from seeing other customers, hit the preview button and voila, they have view and access to the list of customers you don't want them to see. SAVED SEARCHES ARE NOT SECURE - even if restricted to specific roles!
2. One possible workaround? Use Sales Groups and set employees restricted to view only theirs or their teams. This automatically creates a list of customers only associated with the ones where the user is identified as part of the sales group. SEEMS to fix #1, but wait...
Now, create a case (or a transaction or whatever might have a customer record/list field on the form), select 'List' from the customer field and voila, the entire customer list appears, regardless of whether the customer is yours or someone elses. SALES GROUPS WITH RESTRICTED EMPLOYEE AND SALES ROLE RESTRICTIONS ARE NOT SECURE!
What exactly are roles and audiences good for if they do not properly secure the user from working around (fairly easily)?
I should be able to:
1. Assign a customer saved search to replace the built-in one and not allow it to be edited (or even the criteria to be viewed)!
2. Setup a Sales Group that when restricted applies to ALL customer lists, not just the simple dashboard overview lists.
3. Be able to filter built-in list/record fields on forms (or they should comply with the greater access privilege)
This is not good security and provides a false sense of viable security when it isn't. If someone knows workarounds to these, please chime in (with the exception of custom list/record fields and suitelet lists which I will do as a final alternative if can't figure out something).