Backlog
31Under consideration
Allow filters in Analysis to use wildcards
All the filters in Analysis are a “starts with” filter, and sometimes you want to look for anything that came from a .ru domain, or anyone that used a email address that had the word “invoice” in it. But current filters don’t allow that, everything is “starts with” and using something like “*.ru” or “*invoice*@*.*” doesn’t work.
Scheduled Signatures and Banners
We need the ability to schedule signatures and banners to activate and deactivate based on specific dates and times. Use cases: Holiday banners (e.g. display during a holiday break period) Sale/promotion period banners Seasonal email signatures (e.g. "Happy Christmas" or "Happy New Year" that activate and deactivate automatically) Time-sensitive campaigns across the organization Currently these changes require manual updates, which is error-prone and creates unnecessary work for MSPs managing multiple tenants.
Rewriting of banners after user has clicked link
It would be fantastic if, in the vein of Graphus, the banner changed after the user has clicked on a link. For example, if the user clicks Safe or Not Greymail, the banner should change to reflect that they have submitted the email. Otherwise, end users will be confused as to why the email still says warning, danger, etc. and is prompting them to click the link.
DKIM Signing
When you reply or forward an e-mail that has been processed by Inky (banner added) the e-mail will be DKIM signed by Microsoft 365 and then forwarded to Inky to remove the banner. This will break your DKIM signature. Please add the functionality to Inky so it will be able DKIM sign those e-mails.
Add Graymail Label Creation for Google Workspace
On Microsoft deployments MSPs can enable the graymail folder for all subscribers and the individual subscriber can also create the folder. Please extend this to Google Workspace installations.
View Quarantined emails for all clients simultaneously
Currently we can only view the quarantined emails for one client at a time. We would like to have a place where we can view all quarantined emails for all clients at the same time.
Maintaining originating sender IP address
When we look at the header of email processed by INKY we see change sender IP that causes delivery issues and DMARC failures specifically for those customers that use an external mail service. (for example Salesforce). An example for a customer using sparkpostmail.com for relaying: Without INKY: Authentication-Results: spf=pass (sender IP is 192.174.94.29) smtp.mailfrom=bounce.mail.powerall.nl; dkim=pass (signature was verified) Received-SPF: Pass (protection.outlook.com: domain of bounce.mail.powerall.nl designates 192.174.94.29 as permitted sender) receiver=protection.outlook.com; client-ip=192.174.94.29; Received: from mta-94-29.sparkpostmail.com (192.174.94.29) What we see happening is if an email received from that mailservice is routed through INKY the IP address changed so the SPF check fails: Authentication-Results: spf=softfail (sender IP is 18.198.39.243) smtp.mailfrom=bounce.mail.powerall.nl; dkim=fail (signature did not verify) Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounce.mail.powerall.nl discourages use of 18.198.39.243 as permitted sender) Received: from ipw.inkyphishfence.com (18.198.39.243) Besides that, DKIM is also changed so that check also fails. This caused emails to be Quarantined by Microsoft. Is there a way to prevent this behaviour: Now we have to explain to customers that mail that is configured properly still gets quarantined. One customer missed a deadline because of this.
Logo placement of top or bottom or flexible
Wish the logo would have more flexibility in placement (via the custom editor) or an option for above or below. We work with franchise partners who have specific ideas of what they want the signatures to look like.
Add field for additional Work number such as adirect inward dial number
Haivng a additional phone field would halp my receptionist if the sales and service staff could add direct dial number in their signature, alon with the call and main numbers.
Push-button Encryption
I have several customers who I’m trying to move to Inky from other protection platforms. The primary pushback I’m getting is that other providers offer a plugin or dropdown that triggers encryption. The customers’ primary concerns with sending emails for encryption based on typing subject line tags like [encrypt] are based around possible spelling mistakes or other syntax errors. As the encrypted content doesn’t follow clear patterns like SSNs or be counted on to be picked up by Data Type category, they need a proactive way for users to encrypt the messages. Is there any way to implement a button or category to simplify encryption beyond subject line tagging? Is anything being worked on that I can let these customers know is coming to make them open to considering the platform in the future?
Next up
6Committed and queued
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
Quarantine Filter
Please allow us to filter by who quarantined the email, be microsoft or inky etc.
Billable User List
We are new to Inky and operate as an MSP supporting both Google Workspace and Microsoft 365 environments. This is more of a feature request. After reviewing the available documentation and similar articles related to billable users, I don’t see a straightforward way to generate a consolidated list of billable users across both platforms. Currently, the documentation explains how to identify users separately in Google Workspace and Microsoft 365, but it does not provide a way within Inky to view, pull, or export the list of billable users directly. Since Inky is already able to identify which users are billable for invoicing purposes, it would be extremely helpful to have a built-in report or export that shows these billable users. This would allow MSPs like us to verify billing accuracy against our client environments and maintain proper billing transparency. This functionality would significantly improve the billing validation process and add value for MSPs managing multiple platforms.
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.
Team selection resets during page navigation
Avoid Team selection resetting during page navigation Page links should be relative to the selected Team so that navigating to a different page doesn't repeatedly revert to the default organisation. Currently: Enter Admin Center. Select a Team other than the default. Navigate to Partner Center. The selected Team reverts to the organisation's default. Having the URLs of navigational links dynamically include the selected Team would allow the selection to persist between pages, avoiding the current reset-to-default behaviour.
Add SMX to Upstream provider
Hi there, Can we please get SMX Mail (https://portal.smxemail.com) added to the UpStream Provider list?
In Progress
3Actively being built
Inky API
Please provide access to an API to block e-mails and other useful capabilities in order to automate ticket closure.
DMARC Monitoring Page Enhancements
Requested enhancements to the DMARC Monitoring page: Update the green SPF circle to be yellow when the INKY SPF record is NOT present. Update the yellow DMARC circle as well as the yellow SPF circle to work with DMARC and SPF flatteners. MSP-level DMARC report: Ability to see the status of all clients' DMARC settings from a single view. Currently MSPs have to go into each client individually, making it impossible to track which clients/domains are misconfigured.
Add new Arctic Wolf Managed Security Awareness IPs to integration
Just got an alert from Arctic Wolf updating IPs Arctic Wolf issued new IPs for Arctic Wolf Managed Security Awareness. Add the following IP range to the integration in place if needed: 3.42.155.128/29
Done
31Recently shipped
Integration with Autotask
Automated ticket creation would be really great. We have many instances where a customer configures a 3rd party service to send as their own domain (think sendgrid) and we have no clue until someone comes in here and reviews the data via their widgets. If we could instead have tickets automatically created so our techs could be made aware when its flagged, work with the customer to configure the service correctly, and also reduce the false positives in Inky. It would be a massive win/win all around.
Smart Ticketing with Autotask
Integrate with AutoTask Smart Ticketing.
Email Signature Customization — Styling, Layout, & Fields
Typography & styling Per-line / per-field typography — font color, size, bold, and italic for each individual line and data field Team Signature Data styling — per-field bold, color, and size (e.g. company name bold in brand color, username slightly larger than body text) Layout & arrangement Reorder/reposition signature components (custom arrangement) Preview Edit the sample/preview data used in the signature preview
EIN vs SSN
We’ve got to be able to granularity separate EIN (XX-XXXXXXX) and SSN (XXX-XX-XXXX) on the National ID. EINs are public information that can be gotten in 100 places and we need to be able to exclude one or the other via the gui.
Advanced Block List Expiration
MSP Partners are not able to remove the expiration date for advanced block list rules on their own. It is required to open a ticket or reach out in AI chat to have those Expirations removed. This has a negative impact on MSPs managing many customers and results in time wasted for Kaseya and MSP employees. I would like an option to extend advanced Block List rules indefinitely. As an additional feature, the ability to manage Advanced blocklist rules at the partner level so they can be copied down to the customers would also be ideal. Thank You
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.
Integration Between BullPhish ID and INKY User Phishing Reports
We are requesting improved integration between BullPhish ID (phishing simulations) and INKY (email security) to better handle user-reported simulated phishing emails. Current Issue: When a user correctly identifies and reports a BullPhish simulation using the “Report Phish” button, the message is treated as a real phishing incident by INKY. This results in: Unnecessary ticket creation (Autotask PSA) SOC/technician time spent reviewing false incidents User confusion due to lack of feedback Increased noise in phishing reporting workflows Requested Behavior: When a user reports a BullPhish simulation: The system should automatically recognize the message as a simulation (via headers, tagging, or integration). The user should receive immediate feedback such as: “Good catch — this was a simulated phishing test.” The event should be logged in BullPhish as a successful user action. The report should NOT: Generate a phishing incident in INKY Trigger SOC workflows or alerts Create tickets in Autotask Additional Suggestions: Introduce a header/tag (e.g., X-Phish-Simulation: BullPhish) for easy identification Allow MSPs to define handling rules for simulated phishing reports Provide reporting on user detection success without impacting security incident metrics Business Impact: Reduces false positives and alert fatigue Improves technician efficiency Enhances user training experience with immediate reinforcement Aligns phishing simulation outcomes with real-world SOC workflows This integration would significantly improve operational efficiency and the overall effectiveness of the Kaseya security stack.
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.
Banner color applied to signature on replies
There seems to be a bug in that on receiving replies, there is a border around the original signature that is the color of the banner added to the incoming message. Below are a couple of examples. Note that these are on replies that are received (i.e. when I receive a reply from someone I originally sent a message to, my signature appears to have a border around it in the same color as the banner added to the reply message. Seems like it is only internal-facing issue since the banners are removed for external recipients, but it is a bit annoying visually for our internal team.
CSV Import for General Allow List
I want to be able to import a CSV file of allow rules into the general Allow List in the Admin Center. Currently, I have to paste comma-separated values manually, but a direct CSV upload would be much more efficient for managing large lists of domains and email addresses.