Three questions the inbox should answer
The limit is generous enough that most teams will never meet it. We are watching the numbers for a week before turning it on by default. How it works. Anything already in flight w…
The limit is generous enough that most teams will never meet it. We are watching the numbers for a week before turning it on by default.
How it works
Anything already in flight when this went out finishes under the old path. It works the same way on the public site and inside the widget, with no configuration to turn on. The setting lives under Settings, and defaults to the behaviour you already had.
- Enable webhook retries.
- Enable reaction emoji.
- Enable an RSS feed.
- Enable dark mode.
Limits
We rewrote this part rather than patching it, because the old approach ran out of room. Most teams will notice this first on the busiest screen they use.
- Enable an audit log.
- Enable granular email preferences.
- Enable a public API rate-limit dashboard.
- Enable Zapier triggers.
Next steps
Nothing about billing changes, on any plan. We will fold the remaining cases in once we have seen this one hold.
- Enable duplicate detection.
- Enable internal notes.
- Enable an offline mode.
- Enable scheduled digests.
curl -sS https://api.example.test/v2/items \
-H "Authorization: Bearer $BULLETIN_API_KEY"
- security