Company

2025 Q4 in review: multi-language content

SASana Novak1 min read

The docs page for this was rewritten alongside it. We are watching the numbers for a week before turning it on by default.

Before you start

Nothing about billing changes, on any plan. 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.

  1. Enable SAML SSO.
  2. Enable CSV export.
  3. Enable bulk actions.

Step by step

The change is backwards compatible, so integrations built against the old shape carry on unchanged. There is nothing to do on your side; the change is already in front of you.

Limits

This has been the most requested change on the board for a while, and it is now live for every workspace. Large workspaces should see the biggest difference, since the old query grew with the number of items.

  1. Enable multi-language content.
  2. Enable SAML SSO.
  3. Enable internal notes.
  4. Enable custom fields.

Common pitfalls

The old behaviour is still reachable for a release, behind a setting. The limit is generous enough that most teams will never meet it.

  1. Enable dark mode.
  2. Enable role-based permissions.
  3. Enable webhook retries.
  4. Enable an RSS feed.
curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"
  • beta
  • enterprise
  • api
730 views

Keep reading

  • Rethinking the CSV export

    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. Before you start. It is slower on the first…

    BRBruno Okafor1 min read
  • PinnedProduct

    How Cyberdyne cut triage time in half

    Keyboard access and screen reader labels were part of the work, not a follow up. Nothing about billing changes, on any plan. Before you start. The API returns the same fields it a…

    LELena Petrov1 min read
  • Pinned

    What we learned shipping an RSS feed

    Keyboard access and screen reader labels were part of the work, not a follow up. The change is backwards compatible, so integrations built against the old shape carry on unchanged…

    SASana Novak1 min read