Why we rebuilt the dashboard from scratch

Nothing about billing changes, on any plan. The limit is generous enough that most teams will never meet it. Two long-standing reports close with this, and both are linked below.

Step by step

The change is backwards compatible, so integrations built against the old shape carry on unchanged. The docs page for this was rewritten alongside it. Existing setups keep working exactly as they did — nothing needs migrating.

1. Enable board-level moderation.
2. Enable SAML SSO.
3. Enable attachment uploads.

What changes

It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. We will fold the remaining cases in once we have seen this one hold.

Limits

There is nothing to do on your side; the change is already in front of you. We rewrote this part rather than patching it, because the old approach ran out of room. The API returns the same fields it always has, with one addition.

1. Enable custom fields.
2. Enable a Linear two-way sync.
3. Enable internal notes.

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

Common pitfalls

It is slower on the first load and faster on every one after. It works the same way on the public site and inside the widget, with no configuration to turn on. We are watching the numbers for a week before turning it on by default.

1. Enable granular email preferences.
2. Enable changelog email previews.
3. Enable multi-language content.
4. Enable Slack notifications.

Next steps

Most teams will notice this first on the busiest screen they use. If you were using the workaround, you can drop it — the built-in path covers the same ground.

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