How Soylent cut triage time in half, one quarter later

The change is backwards compatible, so integrations built against the old shape carry on unchanged. The docs page for this was rewritten alongside it. Keyboard access and screen-reader labels were part of the work, not a follow-up.

How it works

Anything already in flight when this went out finishes under the old path. The old behaviour is still reachable for a release, behind a setting.

Step by step

Existing setups keep working exactly as they did — nothing needs migrating. We rewrote this part rather than patching it, because the old approach ran out of room. The limit is generous enough that most teams will never meet it.

1. Enable Zapier triggers.
2. Enable keyboard shortcuts.
3. Enable internal notes.
4. Enable SAML SSO.

curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

What changes

The setting lives under Settings, and defaults to the behaviour you already had. Large workspaces should see the biggest difference, since the old query grew with the number of items.

1. Enable webhook retries.
2. Enable role-based permissions.
3. Enable custom domains.

Common pitfalls

We are watching the numbers for a week before turning it on by default. Nothing about billing changes, on any plan. It works the same way on the public site and inside the widget, with no configuration to turn on.