The conversation lives on the item, not in a chat you have to search later.
Open any item and the updates thread is right there: who said what, which file they attached, and what changed. Mark an update internal and guests and clients never see it. Email arrives right away only when something is addressed to you.
Updates, mentions and files
Post an update on an item, reply to one, like one. @mention a member to pull them in. Attach files and images; images open in a lightbox. Everyone subscribed to the item sees it in their notifications.
Boards have a discussion thread too, for things that are about the board rather than one item.
- Updates and threaded replies
- @mentions with notifications
- Likes on updates
- File and image attachments
- Board-level discussion
- Seen-by on updates
Internal updates for the team only
Click the lock before posting and the update is internal: only workspace owners, admins and members can read it. Board guests never see it, and neither do clients on a client portal. Replies to an internal update stay internal.
The rule holds everywhere an update can travel: the app, the REST API and MCP server when the key acts as a guest, notification emails, the daily digest and update counts. Webhooks and Slack messages report that an internal update was posted, without its text.
One click in the update box. Internal updates are marked so the team can tell them apart.
Guests in the app and contacts in the client portal never receive them.
Webhook and Slack events for internal updates carry a flag, not the message.
Notifications and activity
Notifications are quiet by default. Mentions, assignments, replies to your updates and requests for your approval email you right away. Everything else, such as status changes, updates on items you follow, reactions and automation notices, shows in the bell and is collected into one daily digest email instead of a stream of messages.
Each type has its own setting in your profile: show it in the app or not, and email it immediately, in the daily digest, or not at all. Automation notices never email immediately, and you are never notified about your own changes. The digest also lists what is overdue, due today and tomorrow, and newly assigned to you.
Every change is written to the activity log, whether it came from a person, a form, an automation or the API, so the history of an item is complete.
- Immediate email only for mentions, assignments and replies by default
- Daily digest for everything else
- Per-type setting: in app, and email immediately, in the digest, or off
- Never notified about your own actions
Every change from a person, a form, an automation or the API is written to the item's history.
Set yourself as focused, away or out of office so teammates know before they ask.
Jump to any board or item from anywhere with the keyboard.
Questions
Can I turn off email notifications?
Yes. Each notification type has its own email setting, immediate, daily digest or off, separate from whether it shows in the app.
Which notifications email me right away?
By default only mentions, assignments, replies to your updates and requests for your approval. The rest is summarised in the daily digest. You can change each type in your profile.
Who can read an internal update?
Workspace owners, admins and members. Board guests and client portal contacts cannot, and API keys acting as a guest do not receive them.
Can I use TallyWeek on my phone?
Yes. Open it in your phone's browser and add it to the home screen. It runs full-screen with the same notifications.
Is there a chat?
No. TallyWeek keeps conversation on items and boards. Many teams keep their chat tool and paste item links into it, or post board events to a Slack channel through an integration.
Step-by-step instructions are in the docs.
Start a free workspace for your team.
14 days of Pro with no card, then Free for up to 3 members with every view and every automation.