Provide options for restricting views of discrete ...
# ask-stanley-ai
m
Provide options for restricting views of discrete transactions while also omitting them from native reporting for specific users
c
AI generated answer (using internal Slack threads):
To restrict views of discrete transactions and omit them from native reporting for specific users, you can use a combination of role permissions, custom fields, and workflows in NetSuite. Here's a detailed approach: 1. Role Permissions: You can create a custom role that has limited permissions. This role can be assigned to users who should only have a summary level view of financial reports without the ability to drill down to transaction details. This can be achieved by providing access to the report, but withholding access to the actual record. 2. Custom Fields: You can create a custom field in the transaction record, such as 'Confidential'. If this box is checked, only certain roles/users can access the transaction record. This can be applied to related transactions as well. 3. Workflows: You can create a workflow that triggers when the 'Confidential' box is checked. This workflow can return a user error if a user without the necessary permissions tries to access the record. This can help to enforce the restrictions set by the custom field. 4. Department Restrictions: You can also restrict access to certain transactions by department. This can be useful if certain transactions are only relevant to specific departments. 5. Custom Transactions: If the standard transaction types do not meet your needs, you can create custom transaction types and restrict access to them. Please note that these restrictions may not prevent viewing the data via searches. Users with access to saved searches may still be able to find these transactions unless they are specifically excluded from the search criteria. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.833452225
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.802747369
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.801497161
Please provide your feedback on this answer.