Notifications

Lithora notifies you in three places: the in-app inbox, email, and your team's chat tool. Each is configured separately, and each is worth configuring.

The three channels

In-app inbox: The bell in the top bar. Real-time, personal, and the only channel that shows everything addressed to you — mentions, assignments, comments, approval requests from the AI agent, and access requests if you are an admin.
Email: Transactional mail (invitations, access requests, billing) is sent as it happens. Activity is batched into a daily digest so a busy project does not become a busy inbox.
Team chat: Lifecycle events can be routed into Slack or Microsoft Teams per team, so the channel your team already watches gets the update.

Routing events to Slack or Microsoft Teams

A per-team overlay: set nothing and behaviour is unchanged.

Open Integrations › Notification Routing in the integrations control center, pick the team, and switch on the destinations you want for each event. Four lifecycle events are routable — deliberately, because these are the ones the event bus actually publishes:

Events that can be routed to a chat destination
Event	Why you would route it
Task created	New work landing in a project you follow.
Task assigned	Someone put work on a person — including you.
Status changed	Work moved between columns.
Task completed	Something shipped.

Slack destinations take a target channel; Microsoft Teams posts to the connected webhook. Routing is configured by a team owner or admin and applies to the whole team. Connect the tool first — see Integrations.

Tuning what reaches you

Open Settings › Notifications.
Turn channels on or off per event type — mentions, assignments, comments, project updates.
Keep mentions and assignments on everywhere. They are the two that are actually addressed to you personally.
Push broad “something changed” activity to the daily digest rather than instant email, and let the chat routing cover the team-wide signal.

A sane default

In-app for everything, email digest once a day, and chat routing for just Task assigned and Task completed. That gives you one place to catch up, one daily summary, and a channel that only fires when work changes hands or lands.

Who gets notified

Notifications follow team membership, so you are only notified about work in teams you belong to. People viewing a project through a public share link have no account in your workspace at all — they are never notified, and publishing a link does not subscribe anyone to anything.