Why is my user still getting a permissions error when attempting to access a custom record that their role has access to?

AI generated answer (using internal Slack threads):

Based on the conversations, there could be several reasons why a user is still getting a permissions error when attempting to access a custom record that their role has access to: 1. Custom Record Permission: The custom record permission is global to all custom records, not the custom record type. If the user's role has been given permission to a specific custom record type, but not to custom records in general, they may still encounter a permissions error. 2. Access Type: If the Access Type for the custom record is not set to "No Permission Required" or "Use Permission List", the user may not be able to access it, even if their role has been given permission to that custom record type. 3. Record Ownership: If the user is the owner of the custom record, they may still be able to edit it even if their role does not have edit permissions. This could be causing confusion if you're testing permissions by using a user that owns the record. 4. Temporary Glitches: There could be temporary glitches in the system that cause permissions errors. These usually resolve themselves after a short period of time. To troubleshoot this issue, you could try the following steps: - Check the general "Custom Record" permission as well as the permission specific to the custom record type. - Try changing the Access Type for the custom record to "No Permission Required" or "Use Permission List". - Test the permissions with a user that does not own the record. - If the issue persists, it could be a temporary glitch. Wait for a while and try again. Remember, permissions in NetSuite can sometimes be complex due to the interplay between different types of permissions (role-based, record-based, etc.). It's important to thoroughly test any changes to ensure they have the desired effect. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******