Skip to main content

April 2026 Changelog

A full collection of all changes released during the month of April

Updated today

Unified Tagging with Scope & Rewards Groups (Beta)

This beta introduces grouped BBP and Challenge program scope and rewards powered by asset tags, with an opt-in migration path from the legacy setup.
​

What we did

  • Added reward category support to Asset inventory tag categories

  • Launched a new Scope & rewards groups setup flow

  • Added an opt-in migration path from the legacy flow, with the ability to switch back to the old flow if needed

  • Created a Hai migration assistant for customers with the old flow already in place

Why we did it:

Customers with large or complex inventories and reward table structures need a more scalable way to manage scope and rewards. Additionally, Hackers want a clear view of the scope, reward group scope descriptions and rewards. This new view helps them see all they need to see in one place. This beta provides customers with a consistent grouping model tied to asset tagging, keeping program policy aligned across teams.
​

Who it helps:

  • Enterprise customers with large inventories and complex reward tiering

  • Teams running multiple programs with shared infrastructure

  • Hackers, through a clearer view of the scope and available rewards

How to use it:

This is a closed beta. Contact your Customer Success Manager to opt in.

  1. In Asset inventory, create or select an asset tag category for grouped rewards.

  2. Mark that category as a reward category to auto-enforce uniqueness.

  3. Apply tags to relevant assets in that category.

  4. In the program, open Rewards -> Scope & rewards groups.

  5. Select Enable new setup. There is also a Hai migration assistant that can be used to complete the setup.

  6. Select the relevant asset tag category and map one or more tags to each reward group, adding additional reward groups as needed.

  7. Review reward values, with the ability to choose fixed or range per reward group, scope descriptions, and group names visible to hackers.

  8. Apply changes after review is complete by pressing Save.

  9. Review the Scope and rewards page to view what the researchers will see.

  10. If needed, revert to the old flow by pressing the Revert to old flow button at the top of the setup page. (This may not be available after the beta.)

Did this answer your question?