Loading. Please wait...
Changelog
Dated and specific, including the fixes. A product that never publishes a fix is a product whose bugs you find yourself.
A block editor with drag-and-drop reordering, per-keystroke undo and a live preview. Contact rows write their own conditions, so somebody with no mobile number loses the whole line instead of being left with a stranded label, and the generated markup is the nested-table form Outlook actually renders. Blocks can also be reordered from the keyboard, with each move announced. The HTML view is still there for anyone who wants it.
Signatures can carry the directory photo, served from a stable Atlas URL because Outlook for Windows will not render an embedded image. One person’s title or mobile can be corrected without giving them a template of their own, and a campaign banner is defined once and used across clients rather than pasted into each one.
How many people are on the current signature, per client, counted per person rather than per device. A daily check reads back what is actually on each endpoint, so a signature somebody edited by hand shows up instead of staying invisible.
Paste the HTML and the merge fields are converted. A field we do not recognise is reported and left in place rather than dropped, because a field quietly removed on import is a phone number missing from every signature in the company.
Every save keeps the version it replaced, so a bad signature that reached a whole company can be put back. The editor checks for the failures that only appear in a mail client, including the dark-mode case Outlook gets wrong, and previews against a named person in the client directory rather than a made-up record where every field is populated.
Policies, devices and enrolment tokens could be written directly through the data API by any member of an organisation, regardless of their MDM permission. Writes are now service-role only, and a policy can no longer be pointed at another tenant’s enterprise.
Atlas generates the keypair and keeps the private key encrypted, so the certificate request no longer depends on someone running openssl and storing the key themselves. A certificate that does not match the stored key is refused before it can silently break push.
Apple returns a bypass code only while a device is enrolled and supervised. Atlas now asks for it daily until it has one, so a supervised Mac handed back by a departing employee can still be recovered.
When a direct debit failed and Xero moved an invoice back to unpaid, Atlas kept showing it as paid and stopped collecting it. Reversals are now pulled back and the invoice becomes collectable again.
AI triage was marking genuine client mail as spam, where it was hidden from every view. Messages from known contacts are no longer classified that way.
Phone numbers, HR notes and contract files were readable over the data API by any member of the organisation. Those columns are now reachable only through permission-checked paths.
The support tray now runs on macOS alongside Windows and Linux: chat with a technician, raise a request, and see who is helping, from the menu bar.
Quoted history and signatures fold away, inline images from email render in place, and the channel each message arrived on is shown.
Each client gets a sending key bound to one domain that can only mail addresses you list, so a key taken from their website cannot be used to send anything else.
Tokenised portals for taking a new client on, and for handing one over to another provider, with staff review before anything is applied.
Atlas publishes the SPF and DKIM records for a client sending domain where it manages the DNS, and reports exactly which record is still missing where it does not. An existing SPF record is merged, never replaced.
Endpoints are scanned nightly against a PUP and adware library. Removal is routed through the remediation approval flow rather than happening silently.