Share your product feedback!

Please tell us what we can do to make INKY’s Email Security Platform the best product for you.

Inky admin permissions - allow granular control

It appears that Super Admin is required for onboarding customers. This also allows full access to the Inky product. This means that 10+ engineers in our MSP need Super Admin permissions, with the most of rest of the team effectively needing policy management (the second highest tier). Best practice is to provide only the minimum amount of access to do the job required. There should be more granular permissions: -There should be a separate role for user management at MSP level (i.e. an internal MSP IT person owns this role - this typically would not be someone servicing customers day to day) -There should be a separate role that allows for onboarding new customers (i.e. The professional services/projects/onboarding teams should be able to onboard customers without relying on internal MSP support) -Permissions should be separated for access to mail security and signature management (to ensure different staff can be provided access based on their skillset to reduce risk of access to settings they shouldn’t modify)

Steven Richardson About 2 months ago

1
📧

Email Security

In Progress

Native Integration with SaaS Alerts / Kaseya SIEM for IoC Telemetry

We’d like INKY to provide native telemetry integration with SaaS Alerts and Kaseya SIEM to forward actionable Indicators of Compromise. RocketCyber previously integrated with Graphus, allowing phishing telemetry to feed directly into the SOC for correlation and response. That level of ecosystem alignment should exist with INKY. Currently, INKY threat intelligence remains siloed in the console. For MSPs standardising on the Kaseya stack, this limits SOC visibility and cross-platform correlation. Requested capability: • Real-time event forwarding via API/webhook • Structured IoC data including: – Sender domain / envelope-from – URLs and attachment hashes – Threat classification and confidence – User interaction signals where available • Direct ingestion into: – SaaS Alerts – Kaseya SIEM Why this should be prioritised: • Restores ecosystem parity with prior Graphus + RocketCyber integration • Strengthens Kaseya-stack alignment • Enables SOC correlation and automated response • Increases MSP platform stickiness This positions INKY not just as email filtering, but as a SOC-grade telemetry source within the Kaseya ecosystem.

Imraan Sathar About 1 month ago

📧

Email Security

Integrate INKY’s Report Phish Button with MDO User Submissions

Hi INKY team! We rely heavily on INKY’s phishing detection, visual banners, and user-friendly reporting experience—it’s been a huge win for reducing risk. One enhancement that would make the workflow even stronger is the ability for emails reported using the INKY Report Phish button to also flow into Microsoft Defender → User Submissions. Why this matters Many organizations use Microsoft Defender as their central investigation and incident response hub. When reported emails stay only in INKY, analysts lose correlation with Defender’s AIR investigations, incident timelines, and automated remediation. What would help An optional integration that forwards the full reported message (headers, body, attachments, reporter info) directly into Defender’s submissions queue as a “user-reported” item. Customer benefit This keeps all the benefits of INKY’s reporting experience while giving security teams a single, consolidated investigation pipeline—reducing tool switching and improving incident correlation across the Microsoft ecosystem. Thanks for continuing to deliver such strong email security capabilities. This integration would make INKY even more powerful for Microsoft-centric environments!

Jonathan Todd 6 days ago

📧

Email Security