Sistava

Have An Employee Send From Your Own Inbox

New Feature · 2026-08-06

Details

Every employee already has a free built-in email address it can send and receive from the moment it's hired. That's convenient, but it sends as the employee, not as you, and its sending is capped by plan because the address runs on shared infrastructure. Connect your own Gmail or Outlook instead, and an employee sends and replies from your real inbox, under your name, exactly as if you'd typed the reply yourself. It goes out through your actual account, so it lands in your Sent folder, threads correctly, and replies come back to you rather than splitting the conversation into a second thread. There is no monthly sending cap on a connected inbox, on any plan. The connection lives on your workspace rather than on one employee, so you authorise it once with the same one-click flow every other app uses, and every employee you have hired can use it. No app password, no mail server, no host and port to get wrong. Disconnect it and they stop being able to send from it immediately. Reading is instant: an employee can open threads, search, and summarise without asking. Sending is deliberately different. Every send, reply, forward and scheduled send holds for an approval card first, even where you have set that app's other actions to run automatically. A sent email cannot be recalled and it goes out wearing your name, so that stays a fixed rule rather than a preference someone can switch off later. We also never mirror your mailbox into the platform; what we keep is a record of what an employee actually sent. Both mailboxes can be active at once, and the employee does not guess between them. When a request is open-ended enough that the context does not settle it, it asks which address you meant.

What changed