Skip to content

Notifications

You will learn how Tixio tells you about work that needs attention and how to control the signal.

Notifications can appear:

  • In the top-bar bell.
  • In Inbox.
  • By email.
  • As Slack direct messages when Slack is connected.

For a quick event list, read Notification event types.

Notification center

The notification bell in the top bar shows your active unread count. Open it for a compact inbox preview.

The bell preview includes:

  • Up to 20 recent active notifications.
  • A badge for unread count.
  • Mark all read.
  • Archive read.
  • Per-row archive actions.
  • A link to Inbox for the full list.

Open Inbox when you need the full notification surface.

Inbox

Inbox has two buckets:

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

Each bucket can be filtered by:

  • All.
  • Unread.

Inbox groups notifications by project. Notifications without an issue project, such as some cycle alerts or invitation notifications, appear in Other. Project groups can be collapsed, and the collapsed state is reflected in the URL so the view is shareable and restorable.

Notification rows

A notification row usually shows:

  • Actor.
  • Event verb.
  • Issue key when an issue is attached.
  • Issue title.
  • Optional preview text, such as a comment preview, description preview, status transition, GitHub activity, invitation details, or automation message.
  • Relative time.
  • Unread dot when it has not been read.

Clicking a linked notification opens the related issue, cycle, or invitation. Issue notifications remember that you came from Inbox so you can return to the notification list after reviewing the issue.

Read and archive state

Unread notifications count toward the bell badge while they are active.

Common actions:

  • Opening an unread notification marks it read.
  • Mark all read clears unread state for active notifications.
  • Archive moves a notification out of Active.
  • Archive read moves read notifications from the bell preview out of Active.
  • Restore moves an archived notification back to Active.

Archiving is a personal cleanup action. It does not delete the issue, comment, cycle, or other underlying work.

What can trigger notifications

Tixio supports these event types:

  • Mentions when someone mentions you in an issue description or comment.
  • Assignments when an issue is assigned to you.
  • Comments when someone comments on an issue you are assigned to or watching.
  • Status changes when a watched or assigned issue changes status.
  • Due soon when an assigned issue is overdue or due soon.
  • Cycle started when a cycle starts and you have assigned work in that cycle.
  • Invitations when someone invites you to a workspace or project.
  • Pull requests when linked GitHub pull requests change.
  • Commits & branches when linked GitHub commits or branches are recorded.
  • CI checks when linked GitHub CI transitions to failure.
  • Automation alerts when a project automation sends a notification.

For details, read Notification event types.

Watching and mentions

Watching an issue subscribes you to updates. The issue creator is watched by default, and comment authors can choose to watch from the composer.

Mentions are stronger than ordinary watched updates. If someone mentions you in a comment or description, Tixio sends a mention notification instead of a lower priority comment/status notification for the same change.

Mentions are always eligible for in-app delivery. If email or Slack delivery is enabled for mentions, Tixio sends them instantly rather than waiting for a digest.

Delivery channels

Each notification event type can have separate channel settings:

  • In-app: whether the event creates an Inbox row.
  • Email: Off, Instant, or Digest.
  • Slack: Off, Instant, or Digest.

Email and Slack digest events follow the workspace notification digest schedule. The schedule can be daily or weekly and uses an hour in UTC. Weekly digests also have a weekday.

Slack delivery

Slack direct messages require:

  • A workspace Slack installation.
  • Your personal Slack identity linked to Tixio.

If Slack is not installed, the notification settings page links workspace admins to connect Slack. If Slack is installed but your account is not linked, it links you to connect your Slack account.

Slack notifications can be skipped when Slack is not configured, the workspace is not installed, or you have not linked Slack.

Slack can also be used for assistant chat in DMs or bot-owned threads. For that workflow, read Use the Slack AI assistant.

Mutes

Mutes suppress notifications for a project or a single issue in the current workspace.

Use mutes when:

  • A project is noisy but not relevant to you.
  • You need to pause updates from one issue.
  • You are watching an issue temporarily and want to stop receiving updates.

Mentions are not suppressed by mutes. If someone directly mentions you, Tixio still treats that as an explicit attention request.

Defaults

When you have no saved preference row for an event type, Tixio uses defaults:

  • In-app delivery is on.
  • Mentions and invitations default to instant email.
  • CI failures default to instant email.
  • Most other email events default to digest.
  • Slack defaults to off.

You can change these defaults from notification settings.

Next

Continue to Review and manage notifications.