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.

Full-featured HTML Editor

It would be nice to have a full-featured HTML editor with variables for name, position, etc. Unfortunately, working with the predefined variables is very cumbersome and not creative enoug

Conditional signatures & disclaimers for internal vs external email

Introduce the ability to dynamically apply email signatures and/or disclaimers based on whether the email is sent internally (within Microsoft 365 or Google Workspace) or externally (to outside recipients). We have clients who would like to keep internal emails from becoming cluttered and reduce unnecessary bloat. I hope there are other MSPs with similar thoughts.

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.

E-mail signature functionality

Ability to function with Alias domains for multi-entities within a single tenant and users sending e-mail out from multiple Alias domains. Fix the Dark Mode issues when using custom ordering of fields.

Prevent Users from Managing their signatures

We are currently using Codetwo as an email signature solution. One of the thing we love about it is that there is a checkbox to prevent user created signatures in outlook, OWA, and mobile from being used - forcing the Code2 signature to be applied always.

User Fields Automatically sync with 365

No current way as an admin to update user fields like job titles when updating them in 365; the only way is for the user to update it. So if you have to do a mass change, everyone has to update manually instead of forcing a sync to the tenant.

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 custom badges

Clients want to add professional badges specifically to their certification field.

Feature Request

1) Need to be able to move the Icon/Logo to match the height of the signature text on the right. 2) Adjustable padding/spacing (top of the signature and before/after lines) and to be able to use blank spaces to separate text

HTML Full Support in Inky Signature to Modify fields

Allow INKY signatures to be suppressed per message using an email header

INKY currently supports the following message header for controlling its email protection and banner processing: X-IPW-Ignore: True However, this header does not prevent INKY Signatures from applying a signature to the message. Even when X-IPW-Ignore: True is present, the INKY signature processing operates separately and can still append the sender’s configured signature. Requested feature Please add a supported message header that instructs INKY Signatures not to apply a team or personal signature to a specific email. For example: X-INKY-Signature-Ignore: True The exact header name can be determined by INKY. When this header is present, the expected behaviour would be: Do not append an INKY team or personal signature. Apply the exclusion only to the individual message containing the header. Continue any other applicable INKY processing normally. Do not require the sender or mailbox to be excluded from INKY. Ideally remove the control header before the message is delivered externally. Existing behaviour An Exchange Online mail flow rule can currently add: X-IPW-Ignore: True This provides a way to exclude a particular message from applicable INKY protection or banner processing. There is currently no equivalent header for INKY Signatures. Importantly, adding X-IPW-Ignore: True does not solve this requirement because the signature is still applied. The signature component needs its own supported message-level exclusion mechanism. Example use case We sometimes need to forward selected emails to another system for automated processing, such as a ticketing, document-processing, accounting or workflow platform. These messages need to arrive without an email signature being appended. The signature may: Become part of the content being processed. Interfere with automated parsing. Add unrelated contact details or branding. Cause the receiving system to incorrectly identify the end of the original message. Be repeatedly included when a message passes between automated systems. An Exchange Online mail flow rule could identify messages being sent to the processing address and add the signature-exclusion header: Recipient: processing@example.com Add header: X-INKY-Signature-Ignore Value: True The intended flow would be: A message is sent or forwarded to the processing system. Exchange Online adds the signature-exclusion header. INKY processes the message normally. INKY Signatures detects the header and does not append a signature. The external system receives the original message content without additional signature content. Desired outcome This would provide granular control over signature application without having to: Exclude the entire user or mailbox from INKY. Disable the user’s signature globally. Change the signature configuration temporarily. Route the message around INKY. Rely on X-IPW-Ignore, which does not affect signature application. The feature would be particularly useful for messages sent to automated systems, application-generated emails and other workflows wher

Support Animated GIFs for Logo and Footer Images

Allow animated GIFs to be uploaded and preserved for logo and footer images instead of converting them to a static image. This would enable subtle branding, Google Review prompts, promotions, and seasonal banners while remaining compatible with email clients that support animated GIFs and gracefully falling back to the first frame where they do not.

User Opt-In Report for INKY Email Signature

We would like the ability to generate a report that shows which end users have opted in (or out) of the INKY email signature. Currently, there is no built-in report or export available that surfaces user opt-in status for the INKY signature. Administrators have no visibility into adoption rates or who has engaged with this feature across their organization. A report or dashboard view — accessible to admins and super admins — that includes: • Username / email address • Opt-in status (opted in / opted out / never interacted) • Date of opt-in or last change • What profile end-user is using • Exportable to CSV or PDF This data is important for: ✅ Measuring end-user adoption of INKY across the organization ✅ Identifying users who may need additional training or awareness ✅ Compliance and audit reporting ✅ Demonstrating ROI of the INKY deployment to leadership Thank you for considering this request.

Access Users - User Center

Hello, can you add a way to access each individual users - user center so we can manually turn on and off their signature for testing, or to access users whitelists and blocklists and manage it for them.