Get started with Lithi for Mac

Set up EmailOS on an approved Mac, connect one useful source, and review the first result before you expand the work.

Decide what to prepare

Choose one ordinary work pattern for your first review. A routine message or task is easier to assess than an unusual or high-stakes case.

Name the person who owns the setup. Decide which account or work area belongs in the first scope, and keep unrelated information out.

Have your team sign-in details ready. You also need to know which sources your team has approved and what each source may contribute.

Open EmailOS

Install EmailOS from the distribution source your team provides. Open it on the selected Mac and sign in with your team account.

Check the organisation and account shown in the app. If they do not match your plan, stop and correct the account before connecting a source.

Keep the app open while setup finishes. A loading or waiting state is not a ready state, so read any access request before continuing.

Connect one source

Open EmailOS → Settings → Integrations. Add one allowed source, then read the permissions shown by that source’s own sign-in screen.

Choose only the resources needed for your first task. A source is a place that provides context, such as a calendar, project record, or support item.

After connecting, check the visible state before using its information. If you need less context, narrow the selection from the same settings area.

Keep each source separate. Adding another source later makes it easier to understand which context helped and which permission needs attention.

Before you begin a review, write down the question you want the source to answer. Note the account, work area, and person responsible for checking the result. This boundary gives you something concrete to compare after setup.

Do not widen access to solve an unclear result. First check the message, selected source, and visible connection state. Correct that specific condition, then review again.

Review the first result

Open one prepared item and read it in full. Check the audience, factual context, tone, and team guidance before deciding what to do.

Edit wording that does not reflect your intent. Set the item aside when evidence is missing, or ask the responsible teammate when ownership is unclear.

Keep a short note about the source scope and what you observed. A useful note helps another reviewer repeat the setup without guessing.

Keep the scope clear

EmailOS uses the context you select for the local workflow. The portal shows team and account information, but it does not choose a wider source scope for you.

Private messages, drafts, credentials, and customer records stay with the product surface that owns them. Do not paste them into a support request or shared note.

When a source needs a change, return to its connection controls. Make one focused adjustment, then check the next result again.

Recover when setup stops

If the app does not open or sign-in shows the wrong organisation, contact customer support for help with the setup boundary and account questions.

For a prepared item, use Review and send. For the wider data boundary, read the security architecture.

When you are ready for another task, return to Lithi Docs and choose the guide that matches it.