Connect email
Understand your outbound delivery posture and set up inbound forwarding for charter inquiries.
Email works in two directions here: outbound sends (quotes, invoices, statements) and inbound forwarding (charter inquiries landing in your inbox). They're configured differently.
Steps
- Check your outbound posture. Go to Admin → Integrations and look at the Transactional Email row. It's read-only — it reports whether a live provider and from-address are configured for this deployment, it doesn't let you change it.
- Understand what "not configured" means. If outbound isn't wired up, sending a quote or invoice still queues the send — it doesn't fail — but the queued message sits in the outbox and never actually leaves until a provider is configured. You'll see the same honest warning at the point of send, on any screen with a Send button, whenever delivery is off, down, or degraded.
- Get your inbound parse address. Go to Integrations & Feeds → Inbound Email in the console sidebar (this is a separate section from Admin). This page shows the address charter inquiries should be forwarded to — it's provisioned automatically from your tenant slug.
- Set up forwarding from your own mail provider. In your mail provider (Google Workspace, Microsoft 365, etc.), create a forwarding rule or alias on the inbox that receives charter inquiries, and point it at the parse address shown on the Inbound Email page.
- If the address isn't provisioned, the page will tell you — confirm your tenant has a slug set; the address is derived from it automatically.
Outbound delivery is configured by deployment environment variables, not by anything in the console — if the Transactional Email row shows "not configured," that's a platform-side gap to raise with the Obsidian Jet team.
TODO-SHOT: screenshot of the Inbound Email page and the send-time delivery posture banner, from the demo tenant.