Approved senders for message channels (who can auto-start a session)
A per-channel allowlist of who is allowed to auto-start paid work — a session, a reply to the sender, or a workflow — from an inbound text, Slack message, or Telegram message. An unapproved sender still reaches your inbox and still runs your free rules; only the paid parts are gated, and an empty list means nobody.
On this page
What it is
Omniscio can automatically start an AI session or run an automation when a message arrives on a connected messaging channel — a text (SMS), a Slack message, or a Telegram message. That's powerful, but it means whoever can message you could, in principle, kick off a paid AI session (via an automation you set up or a workflow trigger).
The Approved senders list closes that gap. For each of these three channels you keep a small allowlist of who is allowed to auto-start work:
- SMS — phone numbers
- Slack — Slack user IDs
- Telegram — Telegram sender IDs / usernames
An inbound message from an unapproved sender still runs your free rules — archiving spam, forwarding a code to your email, showing a notification, an AI spam-check — and still arrives in your inbox as normal. What an unapproved sender cannot do is drive the paid parts: auto-starting or continuing an AI (Claude) session, auto-replying a text straight back to the sender, running a recipe, or firing a workflow. Only a sender on that channel's list can do those.
Where to find it
Settings → Connections → Channels → open SMS, Slack, or Telegram. When the channel is turned on, an Approved senders card appears. It shows:
- the people currently allowed (as removable chips), and
- an Add box to type a new phone number / ID.
When the list is empty the card explains that no one can auto-start a session yet and invites you to add senders you trust.
How it behaves
The most important rule: empty means nobody
The list is fail-closed: if a channel's Approved senders list is empty, nobody can auto-start a session on that channel. This is on by default and deliberate — so an unknown texter or a stranger in a Slack channel can never spin up a paid AI run before you've said who you trust. To let a sender through, you add them to the list.
Email's list lives in the same place: the Approved Senders box in Settings → Email Inbound is the email row of this one store. One list decides both who may file a bug report by email and which authenticated email senders may start paid automation work. Email's empty list behaves differently from the chat channels: bug intake stays closed unless a Secret Token is configured, while email automations stay open until you add the first address. For SMS/Slack/Telegram there is no such token, so an empty list there is always allow-no-one.
How you'll know it's working (the heads-up note)
Because "empty = nobody," turning this on can pause an inbound auto-start you were relying on. So you're never left guessing: the first time a message from an unapproved sender actually would have started a paid session, reply, or workflow — and only if you have automations turned on — Omniscio drops one note in your Inbox, e.g. "An SMS message was blocked from starting a session because the sender isn't on your approved-senders list." It names an example sender so you can copy the ID straight into the Approved senders box if you trust them. You get one note per channel, not one per message, so it never floods your Inbox.
Note: if an unapproved sender's message only triggered your free rules (a spam-archive, a code-forward), nothing paid was blocked — so no note appears, and those rules simply run.
What it does NOT do
- It does not hide or delete messages, and it does not disable your free rules. A blocked sender's message still shows up in your inbox, and your free automations (archive / forward / notify / AI spam-check) still run — only the paid parts (an AI session spawn, an auto-reply to the sender, a recipe run, or a workflow) are gated.
- It is not a security wall. A sender's phone number / Slack ID can be spoofed, so treat the list as a convenience-and-cost guard (stop surprise paid runs), not as authentication.
- It does not affect read-only channels like RSS, nor webhooks (which use their own
secret token). Email shares the store: its
emailrow (edited in Settings → Email Inbound) narrows authenticated email senders once it has an entry, and any email whose sender the receiving mail host could not authenticate (senderAuthenticated === false) is always gated — see "Under the hood" below.
Related
Email intake is a separate system with its own sender list, described on the Email inbound prescreen page. The inbox a blocked sender's message still lands in is the Inbox overview, and the automations a message can trigger are on the Automations and auto-replies page.
Last verified 2026-11-19