Keep Your Team Security-Aware, Automatically

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. Use Microsoft Graph to read employees, groups, departments, job titles, managers, and directory roles, and subscribe to Microsoft Graph change notifications for users and groups so the audience stays current. 3. Build a monthly security awareness cadence by role: developers receive API, secrets, and dependency security guidance; finance receives invoice fraud and phishing guidance; executives receive social engineering and account takeover guidance; general staff receive password, MFA, and attachment safety reminders. 4. Personalize each message with the employee's role, department, and current risk context, keep it short, include one concrete action, and schedule recurring sends so no team waits for annual training. 5. Run this in MultiMail autonomous mode. Ask me only for Microsoft 365 credentials, approved sender/domain details, brand voice, and any compliance wording needed to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. Use the Google Admin SDK Directory API to read users, groups, organizational units, job titles, departments, and suspended status, and use Directory API push notifications to detect user and group changes. 3. Create a steady security awareness program with role-based tracks: engineering gets secure code and API reminders; finance gets payment fraud and phishing warnings; HR gets sensitive document handling; executives get impersonation and travel-risk guidance; everyone gets practical MFA and credential hygiene nudges. 4. Compose and schedule concise recurring emails through MultiMail, rotating topics, avoiding repeated generic newsletter language, and adapting each message to the employee's org unit, group membership, and role. 5. Run this in MultiMail autonomous mode. Ask me only for Google Workspace credentials, approved sender/domain details, brand voice, and final policy phrases before going live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. Use Okta Event Hooks for user lifecycle and group membership changes, and use the Okta Users API and Groups API to build the current employee audience and role segments. 3. Send ongoing security awareness messages matched to identity risk and role: newly activated users get onboarding security basics; privileged groups get MFA, session, and admin-account reminders; finance groups get phishing and payment-change warnings; executives get impersonation and social engineering alerts. 4. Keep a recurring cadence through MultiMail, personalize each email from Okta profile fields and group membership, and schedule timely follow-ups after relevant lifecycle or group changes. 5. Run this in MultiMail autonomous mode. Ask me only for Okta credentials, approved sender/domain details, brand voice, and the final list of groups that should receive higher-risk messaging.