1. Help Center
  2. Hook Security Updates

Hook Platform Updates - 03.07.23

What's new? Learn about recently added features, fixes, and product releases.

Stay up-to-date with monthly platform updates! These knowledge base articles are curated to empower users with the information they need to get the most out of Hook's platform and services. In this month's article, we cover the new Google Workspace integration, school domain and white-label changes, and a manual report fix for admins.

Added Features: 

Google Workspace Integration Update - If you are currently utilizing Google Workspace, you now have the opportunity to integrate with Google contacts to auto-sync your user targets and groups. If you'd like to learn how to implement this, please click here for setup instructions. Please be aware that this integration pulls over all OUs with no exclusions possible at this time. 

Portal Changes: 

School Domains and White-labeling - As a result of the domain-blocking issues affecting Microsoft email deliverability in February, we are transitioning domains for both the admin and school portals. If you are an administrator, please use your previous credentials to login to the new domain: portal.hooksecurity.net

Your team will now be receiving course notifications and reminders from support@hookecurity.net and be directed to their portal at school.hooksecurity.net. If you have customized your school domain and are experiencing issues with accessing courses, we recommend reading this article about removing white-labeling for more information. 

TIP: Safelist hooksecurity.net and hooksecurity.co to ensure both you and your team will continue to receive important notifications and reminders. 

Please note that if you or your team attempts to access course links from emails sent out prior to February 17, 2023 and they are being flagged as malicious, it is due to the old domain linked within that email. 


Manual Reporting - You may have noticed that the manual reporting feature was not allowing admins to manually log reports after a simulation was complete. This bug has now been fixed and you can continue to manually report. See image below: