Does field level permissions block SuiteQL?

AI generated answer (using internal Slack threads):

Based on the provided Slack threads, it appears that field level permissions do not directly block SuiteQL. SuiteQL is read-only and is used for querying data, not modifying it. However, it's important to note that while field level permissions may not block SuiteQL, they can restrict the visibility and editability of certain fields for specific roles. This is typically achieved through the use of custom forms or workflows. For instance, you can create a custom form and set certain fields' display type as disabled or inline. Then, you can assign this form as the default/preferred form for a specific role. This means that users with that role will not be able to change/edit those fields since the record is loaded in the custom form. Alternatively, you can use workflows to restrict access to certain fields. However, neither of these options prevents someone from searching for the underlying data in a saved search or report. Please note that these are workarounds and can be problematic for keeping track of permissions. Also, if the fields are inline editable, the value can be changed in the search results just by turning on the inline edit function. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******