Why we rebuilt the settings page from scratch

Two long-standing reports close with this, and both are linked below. It works the same way on the public site and inside the widget, with no configuration to turn on.

Before you start

This has been the most requested change on the board for a while, and it is now live for every workspace. It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. Nothing about billing changes, on any plan.

1. Enable SAML SSO.
2. Enable role-based permissions.
3. Enable board-level moderation.

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

How it works

Most teams will notice this first on the busiest screen they use. The old behaviour is still reachable for a release, behind a setting.

1. Enable saved filters.
2. Enable duplicate detection.
3. Enable MRR-weighted prioritisation.
4. Enable custom domains.

What changes

The limit is generous enough that most teams will never meet it. Keyboard access and screen-reader labels were part of the work, not a follow-up.

1. Enable duplicate detection.
2. Enable multi-language content.
3. Enable changelog email previews.
4. Enable vote weighting.

Common pitfalls

The docs page for this was rewritten alongside it. If you were using the workaround, you can drop it — the built-in path covers the same ground. We rewrote this part rather than patching it, because the old approach ran out of room.

1. Enable an offline mode.
2. Enable attachment uploads.
3. Enable a public API rate-limit dashboard.
4. Enable reaction emoji.

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