Skip to content

Review and manage notifications

You will learn how to process your notification inbox, open the right context for each update, and mark or archive items as you go.

Use this workflow when you want to clear the bell without losing important follow-ups.

Before you begin, read Notifications.

1. Check the bell

Look at the notification bell in the top bar.

If the badge is empty, you have no active unread notifications. Open the bell when you want a quick scan of recent active notifications.

The bell preview is best for:

  • A quick unread count.
  • Recent updates.
  • Marking everything read.
  • Archiving read notifications.
  • Opening the full Inbox.

2. Open a notification

Select a notification row to open the related work.

Depending on the event, Tixio can route you to:

  • The issue detail page.
  • A cycle detail page.
  • An invitation route.

Issue notification links include notification context, so the issue detail page can help you return to Inbox after reviewing the issue.

Opening an unread notification marks it read.

3. Use Inbox for longer review

Open Inbox from the sidebar or from the bell preview.

Use the bucket tabs:

  • Active for current notifications.
  • Archived for notifications you moved out of the active queue.

Use the filter tabs:

  • All to see every notification in the selected bucket.
  • Unread to focus only on items that still need review.

4. Review by project

Inbox groups notifications by project.

Use project groups to process one context at a time:

  1. Expand the project with the most important updates.
  2. Open issue notifications that need action.
  3. Mark or archive notifications once handled.
  4. Collapse the project group when you are done.

Use Other for notifications that do not belong to a single issue project, such as cycle alerts and items without a project.

5. Mark notifications read

Use read state to separate "seen" from "not yet reviewed."

Options:

  • Open a notification to mark that row read.
  • Use Mark all read in the bell preview or Inbox to clear active unread rows.

Marking read does not archive. Read notifications remain in Active until you archive them.

6. Archive notifications

Archive when a notification no longer needs to stay in the active queue.

Options:

  • Archive one notification from its row action.
  • Use Archive read in the bell preview to clear read notifications from the preview list.

Archiving does not change issue status, comments, assignments, watchers, or delivery settings.

7. Restore archived notifications

Open Inbox, select Archived, and use the restore action when you archived something too early.

Restored notifications return to Active.

8. Decide whether to act or tune

When a notification is noisy, decide what kind of noise it is:

  • If the underlying issue still matters, keep watching and act on the issue.
  • If the issue no longer matters to you, stop watching it from issue detail.
  • If a whole project is noisy, mute the project.
  • If a single issue is noisy, mute the issue.
  • If an event type is too noisy everywhere, change its channel settings.

For settings, read Tune notification settings.

9. Review a busy inbox

Use this routine when your inbox is large:

  1. Start with Unread in Active.
  2. Process direct mentions first.
  3. Process assignments and due soon items next.
  4. Review watched issue comments and status changes.
  5. Open GitHub and CI notifications only when they affect work you own or watch.
  6. Mark everything read after review.
  7. Archive read notifications when you no longer need the queue.

Next

Continue to Tune notification settings.