Notification Preferences

Every SetGet user can configure their notification preferences to control which channels deliver alerts for each event type. The preferences page provides a matrix view where you can enable or disable in-app, email, and SMS notifications independently for each of the 16 supported events.

Notification preferences are personal to each user and are accessible from Workspace Settings > Reminders > Preferences.

Accessing preferences

1. Click your workspace name in the sidebar.
2. Navigate to Settings > Reminders > Preferences.
3. The event-channel matrix is displayed, showing your current configuration.

Any authenticated workspace member can edit their own preferences. Workspace administrators can also view (but not edit) other members' preferences for troubleshooting purposes.

The event-channel matrix

The preferences page displays a matrix with event types as rows and notification channels as columns. Each cell contains a toggle that enables or disables that channel for that event.

Event type	In-app	Email	SMS
state_changed	Toggle	Toggle	Toggle
assignee_changed	Toggle	Toggle	Toggle
priority_changed	Toggle	Toggle	Toggle
comment_added	Toggle	Toggle	Toggle
issue_created	Toggle	Toggle	Toggle
due_date_passed	Toggle	Toggle	Toggle
label_changed	Toggle	Toggle	Toggle
property_changed	Toggle	Toggle	Toggle
issue_completed	Toggle	Toggle	Toggle
mentioned	Toggle	Toggle	Toggle
date_changed	Toggle	Toggle	Toggle
cycle_changed	Toggle	Toggle	Toggle
module_changed	Toggle	Toggle	Toggle
link_changed	Toggle	Toggle	Toggle
relation_changed	Toggle	Toggle	Toggle
archive_changed	Toggle	Toggle	Toggle

Click any toggle to flip it on or off. Changes are saved automatically.

Default preferences

When a new user joins a workspace, they receive the following default notification preferences:

Event type	In-app default	Email default	SMS default
state_changed	On	On	Off
assignee_changed	On	On	Off
priority_changed	On	On	Off
comment_added	On	On	Off
issue_created	On	Off	Off
due_date_passed	On	On	Off
label_changed	On	Off	Off
property_changed	On	Off	Off
issue_completed	On	On	Off
mentioned	On	On	Off
date_changed	On	Off	Off
cycle_changed	On	Off	Off
module_changed	On	Off	Off
link_changed	On	Off	Off
relation_changed	On	Off	Off
archive_changed	On	Off	Off

The defaults are designed to provide in-app coverage for all events, email coverage for high-importance events, and SMS off for all events until explicitly enabled.

TIP

SMS is disabled by default for all events. Users must explicitly enable SMS for the events they consider urgent enough to warrant a text message. This prevents notification fatigue and unexpected SMS costs.

Channel descriptions

In-app

In-app notifications appear in the notification panel (bell icon in the top navigation). They are:

• Always available (no external configuration required)
• Visible when the user is active in SetGet
• Manageable through mark-as-read and bulk dismiss
• Free and unlimited

Email

Email notifications are sent to the user's registered email address. They require:

• SMTP configured at the instance level
• A valid email address on the user profile
• The trigger or state mapping to reference an email template

SMS

SMS notifications are sent to the user's registered phone number. They require:

• An SMS provider configured at the workspace level (see SMS configuration)
• A phone number registered on the user profile in E.164 format
• SMS enabled for the event type in preferences

Phone number registration for SMS

Before SMS notifications can be delivered, you must register a phone number:

1. Go to Profile Settings.
2. Enter your phone number in the Phone field.
3. Use E.164 format: + followed by country code and number (e.g., +14155551234).
4. Save your profile.

If SMS is enabled for an event in your preferences but no phone number is registered, the SMS notification is silently skipped (no error is logged, but no message is sent).

WARNING

Enabling SMS without registering a phone number results in silent non-delivery. Always register your phone number before enabling SMS channels.

Overriding workspace defaults

Workspace administrators can set workspace-level default preferences that apply to all new members. Individual users can then override these defaults for their own account.

How overrides work

1. The workspace admin sets default preferences under Workspace Settings > Reminders > Default Preferences.
2. When a new member joins, they receive the workspace defaults.
3. Each member can then customize their own preferences by toggling individual cells in the matrix.
4. User-level overrides persist even if the workspace defaults are changed later.

Resetting to defaults

To reset your preferences to the current workspace defaults:

1. Open Workspace Settings > Reminders > Preferences.
2. Click Reset to Workspace Defaults.
3. Confirm the reset.

This replaces all your current preferences with the workspace defaults. Any previous customizations are lost.

Channel priority and interaction

When multiple channels are enabled for an event, all enabled channels deliver independently. There is no priority or fallback logic between channels.

Scenario	In-app	Email	SMS	Result
All enabled	On	On	On	User receives in-app + email + SMS
Email and in-app only	On	On	Off	User receives in-app + email
SMS only	Off	Off	On	User receives SMS only
All disabled	Off	Off	Off	User receives nothing for this event

WARNING

If a user disables all channels for an event type, they will not receive any notification for that event, even if a trigger is configured with them as a recipient. The trigger fires and resolves recipients normally, but the dispatch step respects the user's preferences.

Bulk actions

The preferences page supports bulk actions for efficient configuration:

Action	Description
Enable all in-app	Turns on in-app notifications for all 16 events
Disable all email	Turns off email notifications for all 16 events
Disable all SMS	Turns off SMS notifications for all 16 events
Enable all for event	Turns on all three channels for a specific event row
Disable all for event	Turns off all three channels for a specific event row

These bulk toggles are available via column header and row header controls in the matrix.

Preferences and trigger interaction

Notification preferences and triggers work together in a two-stage system:

1. Trigger stage: The trigger evaluates whether the event matches and resolves the recipient list. This is workspace-level configuration controlled by administrators.
2. Preference stage: For each resolved recipient, the system checks their preferences to determine which channels to use. This is user-level configuration controlled by each individual.

A notification is only delivered if:

• A trigger (or state mapping) exists for the event and includes the user as a recipient.
• The user has the corresponding channel enabled in their preferences.

This means that even if an administrator creates a trigger that sends to all workspace members, each member's preferences determine the actual delivery channels.

Recommendations by role

Different team roles typically benefit from different preference configurations:

Role	Recommended in-app	Recommended email	Recommended SMS
Developer	All events	assignee_changed, mentioned, comment_added, state_changed	due_date_passed only if critical
Project manager	All events	All events	due_date_passed, priority_changed
Team lead	All events	state_changed, issue_completed, priority_changed, due_date_passed	priority_changed (Urgent only via trigger conditions)
Stakeholder	issue_completed, state_changed	issue_completed, due_date_passed	Off
QA engineer	All events	state_changed, comment_added, issue_completed	Off

These are suggestions, not enforced configurations. Each user should adjust based on their workflow and notification tolerance.

Related pages

• Alerts overview --- Introduction to the alert system
• Triggers --- Configure event-based notification triggers
• Templates --- Email template catalog and variable reference
• SMS configuration --- Set up SMS delivery providers
• Alert history --- View send logs and delivery status
• Best practices --- Design an effective notification strategy
• Notification overview --- General notification system
• Email notification settings --- Email-specific notification settings