Notifications that separate action from awareness

Keep assignments and mentions open until they are handled, while routine activity clears naturally after you read it.

Actions need your attention. Updates keep you informed.Product illustration

Why it matters

Make the work clearer, not heavier.

Most work-management inboxes mix responsibility with activity. An assignment, a direct mention, a reaction, and a property change can all look like equally disposable notifications. Taskonio uses fixed product rules to separate events that require a response from events that simply keep you informed.

Designed around the way real teams decide and deliver.

Actions stay open

Assignments and direct mentions remain visible after they are read and require a deliberate done action.

Updates clear naturally

Discussion and work changes become read when viewed and leave the default unread-filtered panel.

The product decides consistently

Fixed classification rules give every team the same dependable distinction without notification administration.

A closer look

How Actions and Updates work in Taskonio.

01

Put responsibility in the Actions tab

When work is assigned to you or someone mentions you directly, Taskonio classifies the notification as an Action. Opening it provides the relevant task or discussion context, but viewing it does not imply that the responsibility has been handled.

  • Assignments become Actions
  • Direct mentions become Actions
  • Opening an Action never completes it automatically

02

Keep Actions until the work is handled

An Action remains in the inbox until you deliberately mark it done. It does not disappear merely because the related work changed or because you opened the notification between meetings.

  • Persistent after viewing
  • Deliberate mark-done control
  • A dependable personal queue for expected responses

03

Let Updates behave like updates

Comments, replies, reactions, status changes, property changes, and other relevant activity enter the Updates tab unless an Action rule applies. With the default unread filter, an Update leaves the active panel after you view it.

  • Discussion and work changes stay visible when new
  • Read state keeps the default panel current
  • Actions never get buried inside routine activity

04

Discuss work without leaving the context

Comments, mentions, reactions, and threaded replies keep the conversation attached to the work. The notification opens the same context, so people can understand why they were notified before deciding what to do.

  • Comments and threaded replies
  • Direct mentions and reactions
  • One path from notification to work context

05

Follow up from email without losing the context

Email notifications provide another way to hear about work that needs attention. Return to the task and its conversation in Taskonio to see the current context and handle the next step.

  • Use email as a notification channel alongside the in-app inbox
  • Return to the task for its current details and discussion
  • Reading an email is not the same as completing an Action in Taskonio

06

Use one clear model across the team

Taskonio applies product-defined rules instead of asking every person to configure a notification system. The model is intentionally small: Actions need deliberate completion, while Updates communicate what changed.

  • Consistent classification across team spaces
  • No rule-builder setup for the inbox
  • Available on every Taskonio plan

How it works

From setup to useful work.

  1. 01

    Receive the signal

    Taskonio classifies an assignment or mention as an Action and relevant discussion or work activity as an Update.

  2. 02

    Open the context

    Read the task, property change, comment, reply, or reaction without losing the distinction between responsibility and information.

  3. 03

    Complete deliberately

    Mark an Action done when it is handled. Let viewed Updates leave the default unread panel automatically.

Taskonio’s approach

An inbox designed around expected response

Actions and Updates reduce the risk of treating a viewed notification as completed work. The distinction stays useful without creating a second configurable workflow inside the product.

Action rules
Assignments and direct mentions enter the Actions tab automatically.
Persistence
Actions remain until the user deliberately marks them done.
Update rules
Comments, replies, reactions, status changes, property changes, and relevant activity enter Updates unless an Action rule applies.
Read behavior
Viewed Updates disappear from the default unread-filtered panel.
Collaboration
Comments, mentions, reactions, and threaded discussion stay connected to the work.
Email
Email notifications bring attention back to the task and its context in Taskonio.
Availability
Actions and Updates are included on every Taskonio plan.

Questions

Know before you switch.

What creates an Action?

Being assigned work or directly mentioned creates an Action through Taskonio’s fixed classification rules.

Does opening an Action complete it?

No. An Action remains open until you deliberately mark it done, even if you have already viewed the related work.

What appears in Updates?

Comments, replies, reactions, status changes, property changes, and other relevant activity appear as Updates unless an Action rule applies.

What happens after I read an Update?

The Update becomes read and disappears from the default unread-filtered panel. You can change the filter when you need to review earlier activity.

Can each user configure classification rules?

No. Taskonio uses a consistent product-defined model so Actions and Updates mean the same thing across the team.

Which plans include Actions and Updates?

Actions and Updates are part of core collaboration and are available on every Taskonio plan.

How do email notifications fit with the inbox?

Email is another notification channel. Return to Taskonio for the current task context; Actions still need deliberate completion in the in-app inbox.

Keep required action from becoming notification history

Give assignments and mentions a persistent home, then let routine updates clear as the team reads them.

Start free