Nocturnal Post — Getting Started (Hosted)
Welcome! This guide is for hosted clients — we run the servers, you just connect your team. Ten minutes from sign-up to your first briefing. (Self-hosting the open-source version? Use the Self-Hosted Setup Walkthrough instead.)
Part 1 — Request access
- Go to nocturnalpost.com and click Request beta access.
- Fill in your name, work email, and team size — tell us a sentence about
how your team works so we can help you set up well.
- We create your tenant (your team's private workspace) and reply with a
sign-in link.
Your tenant is tied to your email domain. Everyone who signs in with
an email at your domain joins the same workspace automatically — and is
isolated from every other tenant. Users on other tenants can never see
your data or trigger your syncs.
Part 2 — Sign in and connect Outlook
- Open your sign-in link and choose Sign in with Microsoft.
- Approve the permissions: read the folders you pick, send briefings on
your behalf, post to a Teams channel if you configure one. Nothing else.
- Your mailbox connects automatically and the Inbox is selected for
syncing. First sync starts within a minute.
You can change which folders are watched any time under
Mailboxes → your mailbox → Folders. Most teams keep Inbox only.
Part 3 — What happens to your email
Every new message is classified on arrival (automatically, no rules to write):
| Category | Meaning | What it becomes |
|---|---|---|
urgent |
time-sensitive, high importance | Work item (high priority) |
follow_up |
asks you to do something | Work item |
needs_response |
a reply is expected | Work item |
internal / external |
from your domain / outside it | noted only |
automated |
noreply, newsletters, receipts | skipped — never creates work |
Work items appear on the Items page and feed your briefings. You can assign any item to a teammate from the Items page dropdown.
What we store: message metadata (subject, sender, recipients, dates) and the first ~500 characters of the body — enough to classify and search, never the full mailbox. It all ages out on the retention schedule (the Vault deletes it on schedule; work items are kept as your to-do list). Full details on the Privacy & Data page.
Part 4 — Your briefings
You'll receive two briefs a day by default, weekdays:
| Brief | Time | What's in it |
|---|---|---|
| Dawn (morning) | 8:00 AM | What needs attention: overdue follow-ups, due today, emails needing your reply, high-priority mail |
| Dusk (evening) | 4:30 PM | What happened today: emails processed, new items, what's completed, what carries overnight |
A weekly Moon Brief summarizes the week every Friday morning.
- Delivered by email to every active team member
- Also posted to your Teams channel once it's configured (next part)
- Test any briefing right now: Briefings page → choose a brief →
Deliver now — nothing waits for tomorrow to verify setup
Part 5 — Set up your Teams channel (recommended)
- In Teams: go to your channel → ⋯ → Get link to channel → copy.
- In Nocturnal Post: Rules page → Teams Delivery Channel →
paste the URL → save. We parse everything server-side; you never need to decode it.
- Send a test: Briefings page → Deliver now on any brief and
watch it post.
The connected user needs to be able to post in that channel (typically
they're a member of the team that owns it).
Part 6 — Rules: instant alerts, not just briefings
Briefings are on a schedule; rules fire the moment a matching email arrives. Create them on the Rules page: name the rule, pick a condition, pick an action.
Four rules worth setting up on day one:
- VIP client escalation — condition Sender domain = your biggest
client's domain → action Post to Teams. Their emails ping the channel instantly instead of waiting for the morning brief.
- Urgent anything — condition Category is
urgent→ Email me.
A safety net that catches high-importance mail outside briefings.
- Billing keywords — condition Subject contains
invoice→
Email me (your AP person's address). Nothing ages past payment terms.
- Regulator / watchdog senders — condition Sender domain = the
regulator's domain → Post to Teams. Compliance-critical mail is never "missed the briefing."
Part 6.5 — Mail security, automatically
While briefings cover what needs attention, Nocturnal Post also watches for threats between briefings:
- Authentication checks — every message's SPF/DKIM/DMARC verdicts
are parsed; failures are flagged.
- Impersonation — a sender mimicking your domain or a watched
client domain (typos, lookalike TLDs, Cyrillic characters) is flagged and, when confident, becomes a high-priority work item automatically.
- BEC protection — executive impersonation, urgent wire/gift-card
language from unknown senders.
- Mail Security section — your Dawn Brief lists flagged messages
so the team sees what was caught without checking anything.
If you're the tenant owner, the Team page shows your monthly service report link — messages processed, security flags caught, briefings delivered: your proof of value.
Part 7 — Invite your team
- Teammates sign in at nocturnalpost.com with **their own Microsoft
accounts (same email domain as you). They appear on the Team** page automatically.
- On the Team page you can:
- Turn each person's briefing email on/off
- See who's active and how the monthly price tapers as you grow
- Assign work items to teammates from the Items page — the evening
brief shows who's carrying what overnight.
Part 8 — Billing: who owns the tenant
Your tenant starts unclaimed — everyone on your domain shares the workspace during beta at no cost. When paid plans activate:
- The first person to start paying takes management of the tenant
(billing, admin settings, ownership).
- Teammates who join later are covered by that plan.
- The price tapers as you grow: **$10/mo for the first user, +$5 for the
second, +$2 for every user after** — a 2-person team pays $15/mo total.
- If the owner ever leaves, ownership can be transferred on the Team page.
Details on the Pricing page.
Questions or problems?
| Issue | Where to look |
|---|---|
| Not receiving briefings | Outbound page shows send status and errors |
| Teams post failed | Re-paste the channel URL on the Rules page |
| Something classified wrong | It's metadata-based; tell us the case via Contact — rules and classification keep improving |
| Data question | The Privacy & Data page, or just ask us |
Anything else: Contact us — we read everything.
Questions about anything on this page? Contact us — we answer everything.