Block your public tasks in your team and prevent data from being exposed due to human error. <\/figcaption><\/figure><\/div>\n\n\nBut this scenario is easily preventable by configuring your account settings correctly. In the team privacy settings<\/strong>, you can control what types of tasks your team members are allowed to create. For example, you could restrict junior analysts to only launch private tasks, while prohibiting them from deleting tasks they’ve created. <\/p>\n\n\n\nIn ANY.RUN, you can launch tasks with 4 different visibility levels: <\/p>\n\n\n\n
\n- Public submission<\/strong>: Anyone can view these tasks, and the information from them is used to improve our threat intelligence services. <\/li>\n\n\n\n
- Who has a link<\/strong>: This setting works similar to a shared Google Doc, allowing you to share access with anyone who has the link. <\/li>\n\n\n\n
- Only team<\/strong>: Visibility is restricted to users connected to your organization’s Master enterprise account. <\/li>\n\n\n\n
- Only me (private)<\/strong>: With this setting, no one except you can view the task. <\/li>\n<\/ul>\n\n\n\n
For companies, you can configure it so that all tasks launched by your team are private, and only the Master account can view them. This can be useful, for example, when you temporarily bring an independent expert on board who doesn’t need to see the contents of your previous investigations. <\/p>\n\n\n\n\n
![\"\"](\"\/cybersecurity-blog\/wp-content\/uploads\/2024\/05\/image-min-1024x565.png\")
![\"\"](\"\/cybersecurity-blog\/wp-content\/uploads\/2024\/05\/image2-1024x585.png\")