Team & account

Manage change digests and read the activity log

Enable daily change emails, inspect who changed a record, and use reminders without confusing them with review completion.

4 min readUpdated

For: Owners managing email preferences; owners and editors reading activity

In this guide

Choose whether to send a daily digest

Open Settings → Email preferences. Under Daily change digest, the owner can enable Email a daily change digest. It is off by default. When enabled, the digest summarizes changes for active Editors and Viewers; no email is sent on days without changes.

  1. Check the restaurant name and the active team list before enabling the preference.
  2. Turn on Email a daily change digest and wait for Daily change digest enabled.
  3. Return to the page to confirm the saved setting. If saving failed, the checkbox returns to its prior value and an error appears.
  4. After a day with changes, ask an intended recipient to check the actual message if delivery needs confirming.

If the page says Email is local on this machine, digests are recorded in the local inbox instead of sent externally. Enabling the preference alone does not establish delivery. A digest is not an urgent alert for every save, so communicate time-sensitive recipe changes directly through your team’s normal process.

Daily email digest controls Enlarge screenshot
The owner can enable a digest of changes for active editors and viewers. No email is sent on days without changes.

Find a saved change

Owners and editors can open Settings → Activity log. Viewers see a message explaining that the log requires owner or editor access.

  1. Use Search activity to search for a person, dish, or change.
  2. Use Activity type to narrow the list, or choose All activity.
  3. Read the subject, summary, person, and time together. A similarly named dish in another restaurant is a different record.
  4. For a dish change, open its linked version history when available. Use the dish’s history to inspect versions rather than expecting an activity row to undo the change.
Restaurant activity history filtered to ingredients Enlarge screenshot
Use the activity type filter to review recorded ingredient changes, including who made them and when.

Act on the change and clear filters

If no activity matches, clear the search and return Activity type to All activity. Check the restaurant selector and confirm that the change was actually saved. Unsaved form edits are not completed restaurant changes.

Use the log to identify what needs checking, then inspect the current recipe and supplier information. The presence of a saved event is not independent confirmation that the allergen information is correct.

Under Reprint reminders, Open menu card takes you to the latest output. Dismissing a reminder only clears that reminder for the current changes; it does not replace paper copies or mark ingredient reviews complete. Finish the print replacement workflow before service.

Keep going

Review or restore a dish version

See earlier dish saves and restore a version while checking it against today’s ingredient records.

Menus & dishes 3 min read

Keep printed cards current after menu changes

Use reprint reminders and a simple service check to replace old PDFs and paper copies after changes.

Sharing & printing 4 min read

Invite teammates and choose their roles

Add editors or viewers, confirm an invitation was accepted, and remove access when responsibilities change.

Team & account 4 min read

Reviewed against the current Dishcard app. Screenshots use sample restaurant data.

Screenshot