v4.0.5: Bring Your Own Mailbox, Keep Your Employees to the Sites You Allow, and Let Them Bring Each Other In

Plenty of businesses run their email on OVH, Ionos or a local host, not Gmail or Office 365. Until now, their AI employees could not use those mailboxes. In v4.0.5 they can. This release also lets you limit the sites an employee may open in your browser, lets employees bring each other into a conversation, and adds one-tap reply buttons on Telegram. It also includes a round of security hardening, with one action for self-hosted admins (see the end).

Bring Your Own Mailbox

The new Custom mailbox connector (Enterprise and SaaS) connects an employee to any mailbox that speaks standard email protocols: OVH, Ionos or any other provider. Go to Settings > Connectors > Custom mailbox, enter the address, pick the employee, then fill in the sending (SMTP) and receiving (IMAP) details. Each side has its own "Test the connection" button, and you can set up sending only or receiving only.

• Sending goes through your provider's own server, from your address, so it is signed by your provider and lands like any other mail from your domain.
• Receiving is instant. The provider tells Geta.Team when mail arrives, so nothing is polled, and new mail reaches the employee within seconds. Mail already in the mailbox stays where it is.
• It does not quietly break. After ten failed connections in a row, the mailbox switches off and the panel tells you why ("wrong username or password", for example), with a "Turn back on" button. Dropped connections reconnect by themselves, and mail that arrives during an outage is delivered once, never twice.
• Passwords are encrypted and never shown again on screen.

The employee's own workspace address keeps working too. Mail sent to either address reaches it, and it can still choose to send from the workspace address when that makes more sense.

Keep Your Employees to the Sites You Allow

Chrome extension 1.3.0 adds Allowed sites. In the extension's settings, switch from "All sites" to "Only these sites" and list the sites your employees may use: a domain, a domain with its subdomains, or a specific path such as example.com/admin. The list lives in your browser and only you can change it.

In that mode, an employee cannot open, read, click, type in or screenshot anything outside the list, and other tabs show up without their address or title. If it tries, it gets a clear error and is told to say so ("I don't have access to example.com: it is not in your allowed sites") rather than look for another way in.

The same release lets one employee work with several browsers. Each browser gets its own name, such as "Chrome - Windows", which you can rename. The employee keeps all of them: with one online, commands go there; with several, it names the one it wants. Connectors > Browser extension lists your browsers, whether they are online, and which employees use each one.

"Paired" also now means it actually works. A pairing that had silently broken, after signing out of the extension or an expired sign-in, now repairs itself within a couple of seconds of the extension connecting. You no longer need to unassign and reassign. Arc users get a small window, since Arc never shows the side panel.

Finally, the extension now shows the app's real chat in its side panel, adapted to the narrow width: history, attachments, tool results, dictation, voice messages and calls. Every future chat improvement reaches the extension without a new extension release.

Employees Can Bring Each Other In

In Messages, an AI employee mentioned in a conversation can now mention others in its reply. Mentioning a person sends them a notification, even if they muted the conversation. Mentioning another AI employee wakes it up to answer in the same thread.

There are firm limits, against loops and runaway costs. An employee can only bring in employees that the person who started the conversation works with. A chain goes three employees deep at most, wakes six in total, and the same employee no more than twice. Past twenty wake-ups per conversation per hour, mentions still show but wake nobody.

Telegram Gets Reply Buttons

An employee can now put buttons under a Telegram message, such as "I approve" or "I'll fix it", so you answer with one tap instead of typing. The choice comes back into the employee's conversation and it acts on it. Once a button is pressed, the buttons are replaced by the choice, so nothing gets approved twice. Bots that are already connected get this automatically.

Gmail, WhatsApp and Other Improvements

• Gmail templates. An employee can resend any email as a brand-new message, with the exact HTML, inline images and attachments, and no "Fwd:" clutter. That makes any email in Gmail a reusable template. It can also mark mail as high or low importance and delete drafts. Replies to an email the account sent itself now go to the original recipients instead of back to the account.
• WhatsApp stops marking messages as read. The connector used to give every incoming message blue ticks, so conversations looked handled on your phone when nobody had opened them. That is now off by default, including on existing connections, with a switch if you want it back. The connector also no longer shows as "online", which had stopped your phone from ringing.
• See where your Gemini bill goes. Usage Overview used to count only voice calls. It now counts every call made with your Gemini key, with a new "By feature" breakdown: meetings, subtitles and dictation, message summaries and translation, image reading, voices and more.
• Export employees on Community. Partners and resellers can now export pre-trained employees from a Community instance. Import is still Enterprise, and when a limit is reached the button is greyed out and tells you why.
• Skill updates you will not miss. The small banner is now a card at the top of the chat, listing which skills have updates, with "Update now" and "Later".
• Messaging, reorganised. In the Team panel, people come first and AI employees last. The Messages page gets its own sidebar plus "People" and "AI employees" filters, so it works as a view of the whole team. Admins can choose to see only their own AI employees or every employee on the instance. A folded conversation window now shows an unread badge and the latest message, like Messenger.
• Cheaper meetings. Action items are no longer extracted live every 90 seconds. You add them by hand during the meeting, and the conversation is read once at the end to catch spoken commitments. Every item still becomes a kanban card.

Security Hardening, and One Action for Self-Hosted Admins

We reviewed every part of the server that answers without a login (104 routes in all) and closed the gaps we found. Several internal endpoints now only answer the instance's own services, licence changes are confirmed with the licence server before taking effect, and the extension's chat panel can only be embedded by the official Geta.Team extension.

If you run your own instance: after updating, regenerate your DKIM key in Settings > Email and update the DKIM record in your DNS. This makes sure no one can sign email as your domain with the old key.

Why This Matters

The common thread is control. Your employees can use the mailbox you already have, stay on the sites you choose, and involve each other only within limits you can see. Bringing in AI employees should not mean changing email providers, giving them the run of your browser, or wondering who woke whom.

Want to test the most advanced AI employees? Try it here: https://Geta.Team