Reminders and notifications

Reminders and notifications are related but different:

• A reminder belongs to an Object and fires at a time you choose.
• A notification is an item in the bell popover, produced by reminders, Workflows, sync, and other app events.
• Captures are incoming content waiting for processing. They live on the Captures page, not in the notification list.

Add a reminder to an Object

Open the Object’s ⋯ menu and choose Set reminder…. The reminder dialog offers these shortcuts:

• In 15 minutes;
• In 1 hour;
• Tomorrow morning (9 AM);
• In 1 week.

You can instead set an exact local date and time. Add an optional note to explain what should happen when it fires, then choose Add reminder.

Reminder times must be valid and in the future. An Object can have more than one reminder.

The same command is available as Add reminder to current Object… in the command palette while an Object is open.

Manage an Object’s reminders

Open Set reminder… again to see its reminders ordered by time. Each entry has a state:

• pending — scheduled but not fired;
• fired — its time has arrived;
• dismissed — acknowledged after firing.

Choose dismiss on a fired reminder to acknowledge it. Choose remove to cancel and remove an entry. Removing a pending reminder prevents it from firing.

Review all reminders in Upcoming

Open Upcoming from navigation or run Open Upcoming reminders in the command palette. Reminders are grouped into time buckets such as overdue, today, this week, and later.

Each bucket shows a count and can be collapsed. A reminder row includes:

• its Object title and Object Type;
• a relative time, with the full date and time available as a tooltip;
• the optional reminder note;
• dismiss for a fired reminder;
• remove to cancel it.

Select a row to open the Object. Upcoming refreshes when reminders fire, and its time buckets roll forward as time passes.

Open the Notifications bell

Choose the bell in the top chrome. Its badge and accessible label show the unread count.

Unread notifications appear first. Read history is collapsed under Earlier and shows up to the 20 most recent read rows. Repeated equivalent events may be grouped into one row with an occurrence count.

From the popover you can:

• select a row to mark it read and open Notification details;
• mark one item read;
• choose Mark all read;
• snooze supported notification kinds;
• dismiss an item;
• run action buttons supplied by a Workflow or notification source.

Closing the popover counts informational notifications as seen and marks them read. Sticky error notifications remain until you retry or dismiss them.

Inspect Notification details

Selecting a notification opens a read-only detail dialog. Depending on the source, it can show:

• kind and received time;
• occurrence count;
• message body;
• a structured payload;
• action buttons;
• Open workflow;
• Open object.

For privacy and storage safety, a payload can be absent, unavailable, or too large to store. The detail dialog states which case applies instead of silently showing an empty value.

Snooze a notification

Only supported notification kinds show a snooze menu. Snoozing hides the item until the chosen time; it does not change an Object’s own date, Task date, deadline, or reminder schedule.

For schedule changes, edit the originating Task or reminder instead.

Notifications versus Captures

The bell contains notifications only. If pending Captures exist, a footer such as “3 in Captures — open” links to the Captures page. Processing or archiving a Capture happens there.

This separation is intentional:

• use Notifications to acknowledge events and errors;
• use Captures to decide what incoming content becomes;
• use Upcoming to manage time-based Object reminders.

Troubleshooting

If a reminder does not fire, confirm that its state is pending and that the scheduled time is still in the future. Keep Lar running or allow the platform’s notification support as required by your operating system.

If a notification action fails, the item remains available and Lar shows an error. Reopen it and retry rather than assuming the originating change completed.

If the bell is empty but Captures are waiting, use its Captures footer or open Captures directly. Captures never appear as ordinary notification rows.