Preview of pull request #446 at 39b4e62. Not the published site.
Skip to content

Manage your notifications

Silo is in active development before 1.0. These guides are updated frequently.

Choose your events and delivery options in the web app under Settings > Notifications. Browser, mobile, email, and Discord delivery work once the person who runs your server has set them up.

Under New Episode Notifications, turn on Enable notifications and Next Up. These choices apply to every delivery channel.

Once you’ve finished an episode of a series, a new episode notifies you when it’s your next one: the first episode you haven’t watched after the one you finished most recently. Episodes that a history import or watch sync marked watched count as finished. Favoriting or watchlisting a series doesn’t make it notify you.

If several episodes arrive together, only your next one notifies you. A later episode that arrives before your next one doesn’t. If you stop partway through an episode, the series doesn’t notify you until you finish an episode. Removing the series from Next Up on Home also stops its notifications.

To check which series will notify you, select See which series notify you under New Episode Notifications. Turn off the switch next to a series to stop its new-episode notifications.

You’re also notified when a title you’re waiting for arrives: one you requested, one you asked to be told about, or one you added to your watchlist before the server had it. These alerts need Enable notifications but not Next Up. If you both requested and watchlisted a title, you’re notified once.

Open Notifications from the main menu. Open a notification or mark it read, or mark them all read to clear the unread count. If an email or mobile alert seems to be missing, look here first.

The Silo apps don’t have a notification list, with one exception: on an Android phone or tablet, tapping an alert that isn’t about a specific title opens an in-app inbox. That inbox is a Beta feature. On other devices, use the web inbox to find older alerts.

Open Silo at its HTTPS address. Browsers only allow notifications from secure addresses, so an address like http://192.168.1.10:8090 won’t work. Ask the person who runs your server for the HTTPS address if you don’t have it.

In Browser Notifications, select Enable and accept the browser’s permission prompt. Other browsers and devices you’ve subscribed are listed in the same section, where you can remove them. Browser notifications are separate from the mobile app’s notifications.

A browser stops getting notifications when you’re no longer signed in there: you sign out, your sign-in expires, you change your password and sign out other devices, or the person who runs your server signs you out.

Sign in on that browser again with the same account and profile. Notifications come back on their own, with no new permission prompt. If they don’t, select Enable again.

Someone else who signs in on that browser doesn’t get notifications until they select Enable. If you don’t sign in there again, the browser leaves the list on your other devices, usually within a day.

After you sign in and choose a profile, allow notifications when the Silo app or your device asks. If you declined earlier, turn them on in your device’s notification settings for Silo. When you tap an alert, the app needs to reach the server to open it.

Your event choices still come from the web settings above.

Email is set per profile, and each profile uses its own verified address, not the account’s sign-in email.

  1. In Email Notifications, select Add address, enter the address, and select Request verification.
  2. Open the link in the verification email.
  3. Turn on Email this profile’s notifications and choose Daily digest, Every episode, or Every episode + daily digest.

Your server may only offer the daily digest. Child profiles can’t receive email notifications.

Switch to your account’s primary profile, entering its PIN if asked, then select Link Discord and authorize the connection. Your Discord account must share a Discord server with the Silo bot.

The link covers every profile on your Silo account, so only the primary profile can turn Discord delivery on or off, change its Frequency, or select Unlink. On other profiles, the section is read-only and asks you to switch to the primary profile.

If Webhooks appears, select Add webhook, enter a name and HTTPS URL, choose which events it sends (Next Up, Requests and watchlist, or both), then use Test. Keep the URL and signing secret private. A webhook can send fewer events than your profile’s choices, but not more.

  1. Make sure you’re on the right profile and its event switches are on.
  2. Look in the web inbox. If the notification is there but no alert reached you, the problem is delivery or device permission.
  3. Make sure your email address is verified, or that the browser or your phone or tablet allows notifications from Silo.
  4. If browser notifications stopped, for example after you signed out or left Silo unopened there for a while, sign in on that browser again with the same account and profile. If Enable then appears under Browser Notifications, select it.
  5. If it still fails, tell the person who runs your server so they can check for failed deliveries.

If your browser says notifications aren’t supported, make sure you’re using the HTTPS address before trying another browser.

A first library scan won’t alert you about every old episode. The server limits alerts for stale events and large batches.