Messages & Notifications

Runnit gives every project, master project, task, and page one shared conversation, and turns activity you care about into notifications you can receive in the app, by email, or through your organisation’s integrations.

Start a conversation

Choose the Messages icon (speech bubble) in the global header. The conversation drawer opens for the page you are on:

On a project, master project, or task, the drawer opens that item’s conversation. Teammates in your organisation share the same thread, so the discussion stays in one place.
On other pages, the drawer opens a conversation for that page.

Messages show the author and time, and the thread keeps its history, so decisions stay attached to the work they are about.

On a desktop, drag the title area to move the Messages window and drag its bottom-right corner to change its width and height. The position and size are saved in your browser. The arrow keys also move or resize a focused handle, and Home resets it. On a smaller screen, Messages uses the full screen.

A project’s conversation is also part of the picture Ru works from. When you ask the assistant where a project is up to or what someone is waiting for, it reads the project’s conversation alongside the comments on that project’s tasks, so a status note written here counts as project status. See Chat Assistant.

When an administrator uses impersonation to check another user’s experience, Runnit reloads conversations and organisation access for that acting user. An authorised project member sees the same project conversation history. If the conversation cannot be loaded, the drawer shows an error instead of an empty thread message.

Mention people

Type @ in the message box to mention:

a person, which notifies them directly;
the project team, which notifies everyone on the project;
a role, which notifies everyone holding that role; or
everyone in the conversation.

Mentioned people receive a notification that links straight back to the conversation.

Direct messages and other conversations

Use the list control at the top of the drawer to switch views:

Conversations lists the threads you participate in, including direct messages.
Mentions lists messages where you were mentioned.

Select any entry to open that conversation without leaving your current page. Direct and private conversations are visible only to their participants.

Notifications

Choose the Notifications bell in the global header to open your inbox. It shows recent notifications with unread items highlighted and a badge with the unread count. From the inbox you can:

select a notification to open the related conversation or item; or
choose Mark all as read.

If the Chat Assistant asks you a question in a conversation that isn’t on screen (you closed the chat window, or moved to another page while Ru was working), you receive a Ru needs your input notification and a short on-screen alert quoting the question. Both take you back to the page the conversation belongs to and reopen the chat so you can answer. Replying clears the notification.

Notifications are raised for activity such as task assignments, project changes, task unblocking, confirmed schedule changes or conflicts, mentions, and messages, based on your organisation’s settings. Schedule notifications also cover blocked-out dates: you’re notified when someone else adds, changes, or removes blocked dates on your schedule, when a task of yours is replanned around blocked dates, and when scheduled work sits on dates that are blocked out. Draft-project schedules are tentative and do not send confirmed-schedule notifications. Email notifications include a link back to the related item in Runnit.

Milestone key dates notify the project team when they fall due and the team and project owner when they become overdue, and the overdue alert also goes to email. Marking the milestone achieved stops these alerts. The overdue email’s button opens the project with the milestone highlighted so you can record it as achieved in one click. The team also sees an in-app notice when someone marks a milestone achieved. See Mark milestones achieved.

Finished projects do not send overdue alerts at all. Once a project is Done, Completed, Cancelled, or Archived, its overdue milestone and overdue task notifications stop, and closing a project marks any key date still open as achieved. Reopening the project resumes alerting for dates it really has missed.

A confirmed booking uses clear schedule copy. For example, a task booking can say “Homepage concepts” has been added to your schedule. Internal system names aren’t included in the message.

Project teams are notified when their project is completed, archived, or unarchived. A status change that completes or archives a project sends one specific notification rather than a generic status-change alert. Conversations on an archived project are read only until it’s unarchived.

You are also notified when a job you started finishes, such as a brief analysis, a background Ru task, image editing, or video generation. A completion notification links straight to the result; a failure notification links to the job queue so you can see what happened. Interactive chat sessions do not raise these notifications.

While you are in the app, a job finishing also shows a short on-screen toast in the bottom right corner, whatever page you are on. View results opens the job’s output (View details on a failure), or the toast disappears on its own after a few seconds. The notification stays in your inbox either way.

Edit system email templates

Organisation owners and admins can edit the emails Runnit sends for account verification, password resets, invitations, form access and confirmations, and every notification type.

Open Admin > Notifications. The page opens on Notification types, where you can switch each notification on or off and mark essential notices as Required for everyone.
Select the Email templates tab, then choose an email type.
Edit the Subject, Heading, and Body. Emails that carry an action link also show a required Button label; emails without one (such as form access codes) have no button to label.
Use only the placeholders listed beside that template. Select a placeholder to copy it, then paste it where its value should appear.
Select Preview to check the email with example values.
Select Save template. New emails for this organisation use the saved version.

If the catalog cannot load, the page shows Email templates unavailable with a reload action. Select Reload templates; if the problem continues, contact your Runnit administrator.

The other administration settings are separated into Delivery channels and Integrations tabs, so they do not clutter the notification on/off list.

Runnit applies the content to a consistent email layout and also creates a plain-text version. Placeholder values are treated as text, so they can’t add scripts or unexpected HTML. Notification preference and unsubscribe links are added automatically and can’t be removed by editing a template.

Select Reset to default to remove your organisation’s version and restore the Runnit default. Account emails use your organisation’s version when Runnit can identify the organisation for that account action. A registration email sent before a person belongs to an organisation uses the Runnit default.

Choose how you’re notified

Open /settings/notifications to set your personal preferences:

Master controls turn an entire channel (such as In-app or Email) on or off for your account.
The table below lets you enable or disable each notification type per channel. Individual settings override the master controls.

Changes save as you toggle them. Organisation rules can force a notification type or channel on, in which case your personal setting cannot disable it.

Administrators can also switch an entire delivery channel (In-app, Email, Slack, or Webhook) off for the whole organisation in the “Delivery channels” section of Admin > Notifications. A channel that is switched off there sends nothing to anyone, regardless of personal preferences or forced notification types, until an administrator switches it back on. Account emails such as password resets and organisation invitations are not notifications and still arrive while the Email channel is off. Non-production datasets are a separate safety boundary: demo, sandbox, and training datasets don’t send notification or invitation email, while account password reset and verification emails still work.

For help from the AI assistant rather than teammates, see Chat Assistant.