> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/release-notes.md). # Release notes What this section records, how the entries are organised, and the version-specific items that change what you have to do during an upgrade. ## What this section is This section records features introduced and behaviour changed in DataDike PAM releases. Entries are grouped by year, then by month, and each one is dated. It is where the version-dependent facts live. Two kinds of entry change what you have to do rather than merely telling you what is new: * entries that state a **restart is required** * entries that record a capability **removed and later restored** Both kinds are on record, which is why the [Upgrade](/pam/deploy-operate/upgrade.md) page treats reading the notes between your installed version and your target version as a prerequisite rather than background reading. {% hint style="warning" %} **Treat this section as a record of notable changes, not as a complete changelog.** Only part of 2026 has entries, not every entry names a version number, and a release with no entry here is not evidence that nothing changed in it. Confirm version-specific behaviour with DataDike support instead of inferring it from a gap. {% endhint %} ## Planned | Release | Planned for | What changes | | ------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **6.0** | February 2027 | **SMS is removed as a multi-factor authentication method.** Accounts that use SMS as their second factor have to move to another method before upgrading | | **6.0** | February 2027 | **A native SAP platform**, with credential rotation and verification carried out over RFC, covering dialog users and the non-dialog account types (system, communication and service) | | **6.0** | February 2027 | **CrowdStrike Falcon as a risk signal.** Endpoint detections are read as an input to the access decision, so a privileged session opened from a host with an open detection can be blocked or sent for approval | {% hint style="warning" %} **This affects the MFA factor only.** SMS as a *notification* channel is not changed: approval requests and just-in-time requests can still be sent by SMS. What goes away is the option to receive the second-factor code by text message at login. Before upgrading to 6.0, move affected users to [another factor](/pam/administration/identities/mfa.md). A user left on SMS when the release lands has no second factor, and how that resolves depends on whether MFA is enforced for them. {% endhint %} Dates and contents of a planned release can change. ## Features introduced in 2026 | Entry | Date stated | Version stated | What it covers | | ------------- | ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | February 2026 | 11 February 2026 | — | Asset-level rule configuration, including Exclusion rules, which allows automation and notifications to be tailored per account or per asset group. Faster credential capture on Linux and on Unix platforms | | May 2026 | 04 May 2026 | — | Reliability and stability improvements to the upgrade process of the gateway VM, with reduced downtime between versions | | June 2026 | 13 June 2026 | 5.0.1 | Granular automation-task permissions: access to automation tasks can be granted through custom roles instead of full administrator privileges. Enforcement of TLS 1.3 between the Gateway VM and the server — **the entry states a restart is required** | | August 2026 | 18 August 2026 | v5.1.0 | Stability of Windows access for Cloud-hosted customers. Reinstatement of custom asset friendly names, which had been removed in error between 5.0 and 5.0.9 | ## The entries that affect an upgrade | Version or range | Item | Why it matters | | ----------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | 5.0.1 | TLS 1.3 enforced between the Gateway VM and the server | The entry states a restart is required. Plan the window accordingly and confirm the gateway side supports TLS 1.3 | | 5.0 through 5.0.9 | Editing an asset to set a custom friendly name was removed in error | If you run a version in this range, the capability is absent. It is a known regression, not something to troubleshoot | | 5.1.0 | That capability reintroduced. Environments that had already renamed assets individually do not lose the customisation | The fix for the range above | {% hint style="info" %} The May 2026 entry is inconsistent about which component it describes: its heading refers to the Broker VM and its body to the Gateway VM. Both are upgraded on their own path, separate from the platform's, so confirm which one applies before planning around it. {% endhint %} ## Items recorded without enough detail to act on Two things in this section are worth knowing about but cannot be turned into an instruction: **Cloud-hosted Windows access and latency.** The August 2026 entry states that for customers hosted in the DataDike Cloud in Brazil, Argentina and Chile, UDP is carried inside the reverse proxy through an HTTPS tunnel served over TCP, and that this protocol change makes access sensitive to latency above 60 ms, which causes interruptions. The entry is headed as an improvement but describes the condition rather than stating what changed. If you are Cloud-hosted and seeing Windows sessions drop, round-trip latency to the hosting region is the first thing to measure. **Three further items in the same entry** — improved identity threat detection and response, a platform design refresh, and support for external AI models — are listed without detail that could be verified against the product. Confirm their scope and availability with support before relying on them. ## Related pages * [Upgrade](/pam/deploy-operate/upgrade.md) * [Back up and restore](/pam/deploy-operate/backup-and-restore.md) * [Monitoring and health](/pam/deploy-operate/monitoring.md) * [Core concepts](/pam/get-started/core-concepts.md)