Notifications
Notifications tell you that something happened that you did not do yourself on the page you are looking at. They appear in the bell menu in the navigation bar, with a count of the unread ones.
What you are notified about
| Notification | Who gets it | When |
|---|---|---|
| New activity | The activity's owner | An activity has been imported, uploaded or synced and stored |
| Duplicate activity | The activity's owner | A stored activity has the same start time as one you already have. It was kept but hidden; open it to unhide it if it is not a duplicate |
| New follower request | The user being followed | Someone asked to follow you |
| Follower request accepted | The user who asked | Someone accepted your request |
| Garmin Connect disconnected | The account owner | Garmin Connect rejected your stored login during a sync. Endurain unlinked the account, and you must connect it again |
| Strava disconnected | The account owner | Strava rejected your stored token during a sync. Endurain unlinked the account, and you must connect it again. Your Strava client credentials stay. If you withdrew Endurain's access on Strava, the notice also gives the day your Strava-synced activities and gear will be deleted unless you connect again |
| Strava data deleted | The account owner | Your Strava-synced activities and gear were deleted because you withdrew Endurain's access on Strava and did not connect again in time |
| Identity provider linked | The account owner | An identity provider was linked to your account |
| Account security changed | The account owner | Your password was changed, reset by an emailed link or set by an administrator; two-step verification was turned on or off; new backup codes were generated; your username was changed; a backup code was used (the notice says how many are left); an API key was created; an administrator revoked your API keys, reset your two-step verification or required a password change; an identity provider was unlinked; repeated wrong passwords or two-step verification codes locked the account; a refresh token that had already been used was presented again and ended one of your sessions; repeated wrong confirmations of a sensitive change ended one of your sessions or locked confirming sensitive changes; or an administrator changed your access type or deactivated your account. See Security notifications |
| Sign-in from a new device | The account owner | You signed in from a browser or app that was not seen before. The first device of an account created in the last 24 hours does not send it; any other first device does |
| User promoted to administrator | Every other active administrator | An administrator gave a user administrator access, by changing their access type or by creating an administrator account. The notice names the user |
| Sign-up waiting for approval | Every administrator | A new user verified their email, or signed up with email verification off, and needs approval. It is created only when email is configured |
If someone withdraws a follow request, the "new follower request" notification it left behind is removed.
Reading and clearing
Open a notification to mark it read, or mark them all read from the menu. Read notifications are deleted after the read notification retention period, 90 days by default. Unread ones are never deleted. An administrator can change the period, or set it to 0 to keep read notifications forever, in Settings → Server settings → Data retention.
How they reach you
A notification is first saved, and then a small message tells your open browser tab to fetch the list again.
sequenceDiagram
participant E as Event (activity stored, follow request, ...)
participant S as Server
participant DB as Database
participant B as Your browser
E->>S: Something happened
S->>DB: Save the notification
S-->>B: Live hint over the WebSocket
B->>S: Fetch notifications
S-->>B: The list
Note over B: The unread count is also polled every 5 minutes (every minute without a connection), and the list is refetched when the connection returns
The live message is only a hint and is allowed to be lost. The saved notification is the record, so a missed hint delays the bell by at most 5 minutes while the connection is open, and a minute without it. For the message format see Realtime updates.
A notification is created at most once per event. If the event is delivered twice, for example after a restart, you do not get a duplicate.
Notifications are created in the background after the event. On a busy server they can arrive a few seconds late, and if a notification is dropped under load it is not recreated. See Background work and failure handling.