Wednesday 19 August
0 accounts
RL
Settings

Configuration

Profile, AI providers, model routing, notification channels and privacy posture. API keys are kept server-side.

Profile

Your identity within RoyOps.

AI providers

API keys stay on the server. Browsers never receive raw key material.

Model routing

Choose which provider and model handles each task type.

Classification
Fast model used to label inbound email by intent and urgency.
Task extraction
Pulls action items from email threads and meeting notes.
Priority scoring
Ranks items for the founder briefing.
Daily briefing / reasoning
Writes the morning briefing across all accounts.

Notifications

Outbound channels for briefings and alerts. Real delivery lands in a later phase.

Send test notification

Watched aliases

Addresses that forward into a connected mailbox. We auto-detect these and tag matching messages.

Used for inbox display and task extraction context. Whatever you list here gets recognised even when To/Cc resolves to a connected mailbox.

Privacy & data

MVP posture — read-only and isolated.

  • · No emails are sent from connected mailboxes.
  • · Calendar events are never created or modified.
  • · Each mailbox is stored in its own tenant boundary.
  • · Secrets live on the server only — Secret Manager in production.
  • · No autonomous outbound actions in MVP.
Secrets are saved server-side. No keys touch local storage.