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

Super Admin is currently required for onboarding customers, which also grants full product access. This means 10+ engineers in an MSP need Super Admin, with most of the rest needing policy management (the second highest tier). Best practice is least-privilege access. There should be more granular permissions: Separate role for user management at MSP level (internal IT owns this, not day-to-day support staff) Separate role for onboarding new customers (professional services/projects teams shouldn't need full admin) Separate permissions for mail security vs signature management (different staff, different skillsets) Granular control over viewing message bodies — currently restricted to Super Admin, but lower-level or custom roles should be able to view message content without full Super Admin access Ability to hide the Subject field by role — all roles can currently see subjects in analysis/observations message lists, and the recent "access denied" on restricted tenants doesn't prevent seeing subjects

Steven Richardson 3 months ago

7
📧

Email Security

Planned

Support Additional Phishing Awareness Training Platforms

MSPs use various phishing awareness and simulation training platforms that need to be recognized by INKY so that simulated phishing emails are not flagged as real threats. Requested platforms: Nimblr — not currently listed as an available awareness training platform. MSPs are working around it using the misconfigured service whitelist option. Cyberhoot — needs to be added as a checkbox option. IPs: 54.240.125.36/32 and 54.240.125.37/32. Quarterly phishing training emails get flagged due to vendor branding in links. Common ask: A standardized way to register awareness training platforms so that their simulation emails are recognized and handled appropriately — not flagged as phishing, brand impersonation, or other threats.

Matt Sywulak 15 days ago

2
📧

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 2 months ago

📧

Email Security

No ability to manage sync

No ability to manage sync for banners or signatures. Currently the M365 groups just state it does a "nightly" sync, which in the IT world is not acceptable. We need to be able to manage and control the sync for when changes or membership updates are needed immediately. This was a frustrating aspect of Graphus and it's disappointing to see the same in INKY. It would be much more helpful if we can initiate a manual sync so INKY can pull updated group memberships and apply banners immediately. Throttling manual sync requests per customer to a daily limit is fine. Also reported as a trust/liability issue: When adding a new user, the dashboard shows them as "active" but they are not actually protected until after the overnight sync. This is misleading — the status should show "Pending" until sync completes. Showing a user as protected when they aren't could create liability exposure.

Sukhjit Singh about 1 month ago

📧

Email Security