John Cusick
11/08/2024, 10:49 PMCeligo AI
11/08/2024, 10:49 PMAI generated answer (using internal Slack threads):Based on the conversations, it appears that NetSuite does not directly support restricting a role to more than one Department segment. However, there are a few potential workarounds: 1. Standard and Custom Roles: You can use standard roles with predefined restrictions or create custom roles. However, creating custom roles can be complex and time-consuming, especially if you have many different roles. 2. Groups: You can create groups of users, where a group has access/restriction to records. This might require some trial and error to ensure it works as expected. 3. GL Segments: You can use GL Segments for permissions purposes. However, this can be confusing when creating reports, searches, and developing workflows, scripts, web services. Everyone involved, including NetSuite Support, will have to be aware that the department field equals "something else". 4. Custom GL Segments: This is a newer feature in NetSuite that might help with your requirements. However, it's important to note that while custom segments have permissions around who can see the segment field itself, there is no way to restrict viewing entire records that have been seen. 5. Scripts: It might be possible to limit the department list based on an account selected on a JE using a script. However, this would require custom scripting and may not be a feasible solution for all use cases. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Celigo AI
11/08/2024, 10:49 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.852719724
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.845744193
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.844783783
Celigo AI
11/08/2024, 10:49 PM