Approve a source
Choose the source your business trusts and keep its purpose clear.
Loading
A business approves a source and its purpose. Each Mac uses only the context its people are allowed to see, and every person stays in charge.
Business context stays useful, limited, and easy to review.
Choose the source your business trusts and keep its purpose clear.
Set who may use it, why they may use it, and when access can end.
Share only the allowed, minimized result, with its source ready to check.
Start with the part of rollout you need to make clear. Each page names its owner, boundary, and next step.
See the team story and the approved-context workflow.
Plan a team rolloutReview members, roles, approved Macs, sources, and revocation.
Review administrationTrace app, provider, team, portal, encryption, and support boundaries.
Review the boundaryPlan stages, ownership, change control, evidence, and rollback.
Plan enterprise adoptionSolo is $12 monthly or $100 yearly, and Pro is $49 monthly or $399 yearly; both are subscriptions. Team and Enterprise are separate plans at $150 monthly or $1,200 yearly per Mac. No plan is metered by message volume. Stripe is the named inbound customer-payment provider, but the public handoff remains contact-only and unverified. Mercury is reserved for Connect payouts, not customer billing.
Eligible inbound replies are prepared locally. The person reviews, edits, skips, or chooses Send.
Approved credentials and readable records stay on the designated connection host Mac.
Only the allowed, minimized result is shared, with a citation people can check.
A support team approves its current service guide for a project group. A teammate asks a question and receives a cited result within that scope. EmailOS can use that approved context to prepare a local draft on the teammate’s Mac. The teammate checks it, edits or skips it, and chooses Send only when ready.
See how Lithi can fit business sources, local drafts, and human review together.