docs Changelog
Launch Nametag Get help

Changelog

The following is a list of changes we’ve made to Nametag, organized by date. Not every change we make is documented here, but we try to include anything that might be relevant to users or administrators.

We often launch new features initially behind feature flags. If you see something particularly exciting, let us reach out to your customer success rep, or email us at help@nametag.co.

August 2025

  • We now request an additional scope from Entra directories (https://graph.microsoft.com/User.Read.All) so that we can read additional user properties from the directory. If you have an existing directory, you’ll see a prompt to reconfigure your connection to add this new scope, but if you don’t need to read additional properties, you can skip this step. (2025-08-28)

  • Updated the documentation to clarify that Entra requires delegated permissions. (2025-08-26)

  • Added experimental support for customizing the behavior of account recovery with the (still experimental) server-side extension mechanism.

    To support this work, we changed the non-public API of the recovery site so that it now receives a signed “intent” for each recovery option which is passed back to the server when the user decides to perform the operation. This prevents foot-guns with user-provided custom logic in extensions. (2025-08-26)

  • Added support for customizing the text shown to users when they are asked to consent to use of biometrics. This uses the still-experimental server-side extension mechanism. (2025-08-26)

  • Fixed a bug on Android where profile photo editing could cause a crash (2025-08-26, version 3.7.34)

  • Clarified the text in the template editor to make it more obvious what the toggle does. It doesn’t disable the template completely, it just hides it from the list of options available for agent-assisted verifications. (2025-08-25)

  • Clarified various text in recovery when flow=enroll is set. We were using text more appropriate to recovery, which could be confusing to users that are receiving initial credentials rather than recovering existing accounts. (2025-08-21)

  • Fixed a bug on Android that caused attestation to fail on certain devices. (2025-08-21, version 3.7.32)

  • Made evidence uploads more robust to unstable or slow network connections on Android. (2025-08-21, version 3.7.32)

  • In the account details view, added a button to unbind an account. In certain relatively rare cases you might need to do this – for example, if an account was bound to an account that was subsequently reassigned to a different person. (2025-08-18)

  • Added additional response fields to the compare selfie API endpoint that describe why a selfie comparison failed. (2025-08-18)

  • Fixed a UI bug where deleting a SAML group mapping caused a client-side error in the Nametag console. Deleting the group worked just fine, but a client-side race condition caused a spurious error message. (2025-08-18)

  • Added a new API to delete profile photos from an account (2025-08-18)

  • Added support for customizing the success messages displayed to users after they complete an account recovery operation. (2025-08-18)

  • Added support for additional image formats for account photos. (2025-08-18)

  • We now use the user-provided account identifier (for example, their email address) as the request label for recovery verifications. This should make it easier to tell which verification request corresponds to which user. (2025-08-17)

  • Fixed a bug that can cause Entra sync to fail under certain rare conditions (2025-08-13)

  • Added support for reading a birthdate property from Entra accounts (2025-08-13)

  • Fixed an issue on some Android devices where users will see a purple prompt relating to operating in full screen mode. (2025-08-12, version 3.7.21)

  • Improved handling of requests that originate on mobile web on Android (2025-08-07, version 3.7.17)

  • Updated documentation for Entra to answer a frequent question about how we authenticate and why we have to use delegated authentication rather than application authentication. (2025-08-06)

  • Improved handling of requests that originate on mobile web on iOS (2025-08-05, version 4.62.1)

  • Improved on-device detection of Malaysian IDs on iOS (2025-08-04, version 4.61.3)

  • Improved handling of devices that lack a depth map sensor, or where the depth map sensor is broken. (2025-08-04, version 4.61.3)

  • Added experimental support for server-side extensions. This new feature allows you to write TypeScript programs that modify and customize certain aspects of Nametag. For now, this feature is disabled with a feature flag. If we have created customizations for you, we will be migrating these customizations to the new framework, and you might start to see an advanced tab in the console that includes your customizations. Eventually, this will become part of our public API contract, but for now we’re still fine-tuning the extension interfaces. (2025-08-01)

July 2025

  • Added experimental support for client-side script and style customization. This feature allows you to inject arbitrary JavaScript and CSS into end-user facing web pages such as the recovery microsite. If we have created customizations for you, we will be migrating these customizations to the new framework, and you might start to see an advanced tab in the console that includes your customizations. Eventually, this will become part of our public API contract, but for now we’re still fine-tuning the extension interfaces. (2025-07-29)
  • Improved on-device detection of Malaysian IDs on Android (2025-07-29, version 3.7.14)
  • By popular demand, we’ve started publishing this list of changes we make to the product. (2025-07-29)