Notifications are short notes to you alone: a game you watch spiking, a review requested from you, a contract you are on changing. They appear under the bell in the top bar, on the Notifications page, and on your phone or computer once you turn that on. Every kind is on by default; turn kinds off in Settings, Notifications.
The bell in the top bar
The badge on the bell is your unread count, up to "99+". It is checked when a page opens and every 30 seconds while the tab is in view (backing off to every 5 minutes while the studio does not answer); a hidden tab stops checking and checks again when you return to it.
Opening the bell shows your latest 20, split into Today and Earlier by your own clock. Choosing one marks it read and opens its page. Mark all read clears every dot; See all opens the Notifications page.
On a phone the bell opens as a sheet from the bottom of the screen.
The Notifications page
At /notifications, also in the Overview rail after Watching, and on g then n.
Every notification, newest first, grouped Today, Yesterday, Earlier this week (from Monday) and Older, in UTC days like every other date in the panel.
Each row has the kind's icon, the title, the whole text and how long ago; an unread one has a dot and a faint wash. Opening it marks it read and goes to its link.
Filter with the tabs at the top: All, Watchlist, Code, Studio, Points and shares, Contracts, and Admin for owners. The filter is kept in the address (
/notifications?group=watchlist; alsocode,studio,points,contracts,admin).The first 30 are shown; Load more adds 30 at a time.
Mark all read in the header marks everything read; marking here updates the bell at once.
What you are told about
One group per kind of work. Each notification opens the page it is about.
- Watchlist
A watched game spikes or drops in players, sets a record, updates on Roblox, changes its name, icon, genre or price, enters a discovery sort, breaks out, or passes a visits or favorites milestone. Opens the game's page (a discovery notice opens that sort on Discovery).
- Code
Someone asks for your review, your pull request is merged or gets changes requested, a repository publishes a release. Opens Reviews, Pull requests or Releases.
- Studio
A studio game is released or goes public, sets a player record, or Roblox reports a new day of its revenue (the amount is in the text). Opens the game's studio hub.
- Points and shares
A game you made is released or earns its bonus point; a game you did not make goes on sale or enters its last week of sale; your unspent points expire this week. See Points.
- Contracts
A contract you are on is drafted, edited, proposed for your signature, replaced by a new version (or your signature cleared), signed or approved; you are removed from a project. Opens the game's contract.
- Admin (owners)
A collector job's last 3 runs all failed, or snapshots stopped arriving for 15 minutes; and when it recovers. Opens the Collector page.
Why you are not told the same thing twice
Each kind waits before telling you again about the same game or subject: for example 6 hours for a watched game's spike, a day for a breakout or a review request, 30 days for a studio game's release; milestones, merges and releases are told once. When more than three watchlist alerts of one kind reach you in one run, they are folded into one summary that opens the Watching page.
Every wait, kind by kind
The watchlist's waits are on What watching tells you. The others:
- Review requested
A day per pull request.
- Pull request merged, release published
Once ever.
- Changes requested
Once per review.
- Studio game released
30 days per game.
- Studio player record
6 hours per game.
- Studio revenue day
Once per day of revenue.
- Points earned, shares on sale, sale closing
Once per project.
- Points expiring
Once per week.
- Collector failing
6 hours per job, told once until it recovers.
- Collector recovered
1 hour per job.
How quickly notifications arrive
Contracts and the bonus point are written the moment the change happens.
Everything else is found every 5 minutes from data the collector already stored, so it can be up to a few minutes behind what happened (finding it asks Roblox and GitHub nothing).
A notification reaches your phone or computer within about 15 seconds of appearing under the bell.
How a notification reaches you
To get a notification to your phone, the platform stores it, sends a Web Push message through your device's push service, and lets the phone display it. Turn phone notifications on first in Settings, Notifications.
Two things write notifications: the API, the moment a contract changes or a share earns the bonus point, and the worker, which checks stored data every 5 minutes. Each is stored once, under your bell, which the panel asks about every 30 seconds. Every 15 seconds the worker also sends new ones to each phone and browser you turned on, through that device's push service, and the device shows it even with the panel closed.
On your iPhone
An iPhone or iPad (iOS 16.4 or later) shows notifications from Blockout once it is on your Home Screen. A Safari tab cannot receive them.
Add Blockout to your Home Screen
Open the panel in Safari, tap the Share button, then Add to Home Screen, then Add.
Open it from the Home Screen
Open Blockout from your Home Screen (not from Safari) and sign in.
Turn notifications on
Go to the studio's Notifications page, tap Turn on for this device, then Allow.
Check one arrives
Tap Send a test notification.
On Android or a computer
Chrome, Edge and Firefox (and Safari on a Mac) receive notifications in an ordinary tab; on Android the Home Screen app works too.
Open the settings
Open the studio's Notifications page in the browser you want them in.
Turn this device on
Choose Turn on for this device, then allow notifications when the browser asks.
Check one arrives
Choose Send a test notification.
What a phone notification looks like
Each one pops up with the studio's icon, even when the panel is closed, and tapping it opens its page (or the window already on it). The app's icon shows your unread count, and reading your notifications clears it. Each device gets the kinds you switched on, as the bell does. A phone that was offline gets only the newest notification of a kind about one thing when it comes back.
Removing a phone or browser from notifications
Your devices, in Settings, Notifications, lists every phone and browser you turned on, with This device marked. Remove one to stop its notifications. You can have up to 10. Send a test notification sends one to every device and says how many it reached.
When a device stops answering
A device whose push service refuses or does not answer rests a minute before it is tried again, doubling up to six hours; the tenth failure in a row removes it. A device the browser unsubscribed (or whose app was deleted) is removed at once. What a resting device missed stays under the bell. Turn it on again from Settings, Notifications.
What is not notified yet
Someone buying a share of your game, unless it earns you the bonus point. The Points page shows every purchase.
A notification more than an hour old when your device was due it, or sent while your device's push service was refusing: it stays under the bell only.
Behind the page: the notification routes
Every route is the signed-in person's own; changes need the x-requested-with header.
GET/v1/notifications
The newest first: limit 1 to 50 (20 by default), before the last id of the page before, and
group or kind to filter. The answer carries unread, counted over every kind.
GET/v1/notifications/unread-count
{ "unread": 3 }: what the bell asks for.
POST/v1/notifications/read-all
Marks every unread one read; POST /v1/notifications/:id/read marks one.
PUT/v1/notifications/preferences
Turns kinds on or off, { "kinds": { "watch_spike": false } }; a member setting an Admin kind is
refused with 403.
The watchlist rules and their waits.
Turn kinds and devices on or off.
The Home Screen app.
Updated