Settings

All SyncUp configuration lives in the Settings tab, which sits at the right end of the tab bar. The tab has a sidebar with four sections; some are admin-only.

👤 Your Role

Shows the role currently assigned to you (Developer, Scrum Master, or Product Owner) and how that maps to your Daily Brief.

• Non-admins see their role as read-only and a note to contact a project admin to change it.
• Admins see a hint pointing them to Team Roles for managing assignments.

👥 Team Roles (admin only)

This is where role assignments are made. SyncUp does not auto-infer roles from Jira project roles — every assignment is explicit.

1. SyncUp lists all members of the active sprint.
2. For each member, pick one of:
   • Developer (default)
   • Scrum Master
   • Product Owner
3. Click Save Roles.

A member’s role is shared across the entire project, not per sprint. Changing a role takes effect on the next Daily Brief load.

⚙️ Preferences (per-user)

The only personal setting today is Alert Sensitivity, which controls how many alerts your UI shows.

Level	Behavior
Low	Critical alerts only (HIGH severity, narrowed).
Medium (default)	Important alerts (HIGH + most MEDIUM).
High	All alerts — including LOW (milestones, etc.).

This is purely a display filter — alerts are still stored at full fidelity in Forge SQL. You can change it any time.

🔔 Notifications (admin only)

Configures the optional daily email briefing.

Toggle

• Daily Briefing (on / off) — master switch.

Schedule

• Standup Hour — choose between 07:00 and 14:00 (one hour buckets).
• Timezone — UTC, Europe/Istanbul, Europe/Berlin, Europe/London, US/Eastern, US/Pacific, Asia/Kolkata, Asia/Tokyo.

The hourly cron trigger fires each hour; when the current hour matches your standup hour in the chosen timezone, the email is sent to all sprint assignees.

Channel

• Jira Email Notifications (on / off). The delivery mechanism uses an internal “anchor” issue created by SyncUp and watched by sprint assignees — Jira’s notification system handles the actual email. This is what the write:jira-work scope is used for (and only this).

Buttons

• Save Notification Settings — persists your changes.
• 📧 Send Daily Brief — sends an immediate one-off email of the current daily brief. Useful for testing the channel.
• 🏁 Sprint Report — sends an email of the most recent closed sprint’s autopsy. Also a one-off, on-demand send.

A success / failure message appears below the buttons for ~5–8 seconds after each action.

What’s stored where

Settings persist to Forge SQL in your tenant:

Setting	Table
Your assigned role	team_roles
Alert sensitivity	user_preferences
Notification config	notification_settings

Nothing is sent to external services. See security for details.

What’s not yet configurable

These are sensible roadmap items that aren’t in the current build:

• Per-project stale threshold (currently fixed at 5 days for Decisions Needed; 3 days for in-progress yellow→red)
• Excluded issue types (everything in the sprint counts today)
• Estimation field (velocity is tracked in issue counts)
• syncup-ignore label opt-out
• Snooze action on alerts (only Dismiss exists)

If any of these block you, tell us at support@bytera.tech.

Next

• Daily Brief — what each role sees once roles are assigned.
• Troubleshooting & FAQ — common questions about behavior.