Rethinking SSO login

Keyboard access and screen-reader labels were part of the work, not a follow-up. Two long-standing reports close with this, and both are linked below.

Before you start

It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Existing setups keep working exactly as they did — nothing needs migrating. Large workspaces should see the biggest difference, since the old query grew with the number of items.

How it works

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

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

What changes

There is nothing to do on your side; the change is already in front of you. The limit is generous enough that most teams will never meet it. Nothing about billing changes, on any plan.

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

Limits

The setting lives under Settings, and defaults to the behaviour you already had. It is slower on the first load and faster on every one after. If you were using the workaround, you can drop it — the built-in path covers the same ground.