Delivery, Messengers, and Email assistant

Delivery, Messengers, and Email assistant in Admin are the company-level switches that connect Ian On to outside services. They're where you decide what's allowed before anyone turns it on for themselves.

Only people with the Owner or Admin role can set up these screens. If Delivery, Messengers, or Email assistant doesn't appear in the Admin menu, check that Delivery, Messenger Bots, and Email Assistant are on under Add-on features in Admin → Features. All three features are off at first. The email assistant works only when both are on: the feature here and Enable Gmail assistant below.

Outbound delivery (Delivery)

Admin → Delivery governs how results leave Ian On. Use the tabs at the top to move between Delivery connections, Delivery rules, Gmail delivery policy, Installed plugins, and Plugin marketplace.

• Personal-account override policy on the Delivery connections tab — for Gmail and Notion separately, you decide whether delivery may be sent through a member's personal account. The default is Block. Even if you allow it, an enabled organization connection is used first when there is one. (This is about delivery channels — the Gmail assistant is a separate switch, under Email assistant below.)
• Current organization connections on the Delivery connections tab — see the delivery connections your organization shares (global or team-scoped) and their status, and Enable, Disable, or Delete them.
• Delivery rules — an auto-send engine. When a piece of work finishes, a rule can route its result to a delivery channel automatically. Personal work is never sent by any rule. A rule created by a member sends team work only while that member belongs to the team. Older rules with no recorded creator skip this check. Each rule has filters (team, agent, tag, artifact path) and a Test that shows how many pieces of work completed in the last 7 days match its filters. If there are too many completions to check them all, it tells you so.
• Gmail delivery policy — a recipient domain allowlist. Gmail delivery stays off until you add at least one allowed domain, so mail doesn't go to unintended recipients.
• Installed plugins and Plugin marketplace — manage delivery plugins. In Plugin marketplace you can install only plugins from registries your organization has approved: check the permissions in Review required scopes, then press Allow and install. In Installed plugins you can Enable, Disable, Check for updates, Edit configuration, and Remove.

Discord bot (Messengers)

Admin → Messengers is where you set up the Discord bot that powers the /ian command. Create an app in the Discord Developer Portal, then enter its Public Key, Application ID, and Bot Token on this screen and press Save. Next, press Register commands, and paste the Interactions Endpoint URL shown on the screen (a public HTTPS address) into the Discord Developer Portal. The full steps are in the Setup guide on the screen. Once the bot is ready, each member links their account with /ian link, then uses /ian ask and /ian report.

Gmail assistant (Email assistant)

Admin → Email assistant is the master switch for the Gmail assistant. Three things live here:

1. Enable Gmail assistant — the on/off switch for the whole organization. While it's off, no one can connect Gmail, and checking of connected inboxes stops too.
2. OAuth Client ID and OAuth Client Secret — the values of your company's Google OAuth app, used when members connect Gmail. A saved secret is never shown again; it only shows as Saved.
3. Polling schedule (cron) — how often Ian On checks connected inboxes for new mail, set as a cron expression. Leave it blank to check every minute. A changed schedule takes effect after the server restarts.

Turn it on here first; then members connect their own Gmail from Settings.