May 2026 Release

Production Release Date: May 27

Product Updates

Recognitions Advanced Rules

The Recognitions builder now supports advanced rules for defining who can give and receive recognitions. Previously, the Studio builder only allowed groups/group classes to be connected using AND or OR, but not both. With Advanced rules, you can create more complex rules such as Group A and Group B or Group C.

Recognitions Builder Rule Example

Product Fixes

Fixed an issue in the Impact block's All Missions view where the Filter text and Search field overlapped at smaller screen sizes. Now, the Filter label is hidden on smaller screens.
Fixed an issue where the error message did not explain why creating a Studio user failed.
Fixed an issue in Data Import where you couldn't navigate beyond the first page of uploaded files.
Fixed an issue in Nitro Studio list views where the page number always displayed as Page 1 even when navigating beyond the first page.

Discontinuation Notice

Legacy OAuth Tokens

Effective with the June 2026 release, legacy OAuth tokens used with blocks will be deprecated.

What this means for you?

Impact and Recognitions blocks will require a JWT gamification token from the /gamification-token API.
Legacy OAuth tokens will no longer be supported for blocks, and new features released in blocks may not work with the old token.
If your program uses both blocks and web components, you must use two separate tokens:
- A JWT gamification token for blocks
- A legacy OAuth token for web components

To prepare for the upcoming token deprecation, you should take the following steps before June 2026.

Review the token used in your Impact block to ensure you’re using a JWT gamification token.
Review the token used in your Recognitions block to ensure you’re using a JWT gamification token.
Update your embed code to use a correct token if you're not using a JWT gamification token in all of your blocks. Use the steps detailed here to update.
Ensure you have two tokens enabled if you have both web components and blocks in the same environment:
- A JWT gamification token for blocks
- A legacy token for web components

Legacy OAuth tokens used in web components will continue to be supported until the official end-of-life date for web components is announced.