<style> /* Reveal x-cloak content so sidebar branch lists and closed-state chips render — EXCEPT the mobile slide-in backdrop, which would otherwise cover the whole viewport in black/40 with no way to dismiss (the dismiss handler is x-on:click="mobileHeader = false" and can't fire without Alpine). */ [x-cloak]:not([x-show="mobileHeader"]) { display: revert !important; } /* (1) Force every version card OPEN so all release-notes content is visible. Overrides the default `.rn-ver-body { grid-template-rows: 0fr }` from release-notes.css, which is normally lifted to `1fr` via Alpine's `:class="{ 'rn-ver-body--open': open }"`. */ .rn-ver-body { grid-template-rows: 1fr !important; } /* (1b) Strip `hidden="until-found"` from collapsed card bodies. WEB-3164 added that attribute on cards 2..N (the first card omits it, see the `{% unless forloop.first %}` in release-notes-cards.eleventy.liquid) so Chrome/Edge browser find-in-page can reveal text inside collapsed bodies and fire a `beforematch` event Alpine catches to pop the card open. Alpine's `x-effect` directive normally removes the attribute when `open` flips true — but without JS that directive never runs, so cards 2..N stay hidden via either `content-visibility: hidden` (Chrome/Edge/Safari 17+ resolve `hidden="until-found"` to that) or `display: none` (older Safari / unknown browsers treat it as a plain boolean `hidden`). Rule (1) above lifts the SCSS-based grid-rows collapse but does NOT override `[hidden]` — the attribute applies a higher-priority `display: none` / `content- visibility: hidden` that wins over grid-template-rows. This rule covers both browser-engine paths: `display: revert` restores the element's normal display (the `grid` utility on the wrapper), `content-visibility: visible` overrides the modern-browser path. */ .rn-ver-body[hidden] { display: revert !important; content-visibility: visible !important; } /* (2) Hide controls that can't do anything without JS so the UI doesn't lie about being interactive: the expand/collapse chevron, the closed-state category chips (Security 3 / Features 5 / …), the section-level expand-all toggle if reintroduced, and the cursor-pointer hint on the header. */ .rn-ver-chevron, .rn-ver-chips, .rn-toggle-all { display: none !important; } .rn-ver-header { cursor: default !important; } /* (3) Hide status pills (Current / Beta / Extended maintenance) and the matching sidebar dots. Pills are rendered server-side from productInfo.json at build time and are accurate at publish — but a stale cached page in Sparkle could surface them on a version that is no longer "Current" by the time the user opens RDM, so hiding them entirely under no-JS removes the whole class of misleading-stale-pill failure modes. */ .rn-ver-tag-line, .rn-status-pill, .rn-status-dot { display: none !important; } /* (4) Sidebar branch chevrons stay frozen in the "closed" rotation without Alpine to flip them — drop them since the branch lists below are already revealed by the x-cloak rule above. */ .rn-toc-branch-head > span:first-child { display: none !important; } /* (5) Hide mobile-only chrome whose Alpine click handlers can't fire: the top mobile menu-open bar and the sidebar's mobile close bar. Both gate `mobileHeader`, which never toggles without JS. */ .rn-main-header, .rn-sidebar > div:first-child { display: none !important; } </style>

Release notes

Release notes

Try it before you trust it: Meet the Devolutions on-demand Lab

Steven Lafortune · July 23, 2026

Table of contents

Testing new IT tools always comes with a question: where do you actually test them? Your production environment is off the table: nobody wants to poke around privileged access controls on systems that matter. And spinning up your own sandbox takes time most teams don’t have.

That’s exactly the gap the Devolutions Lab fills.

What is the Lab?

The Devolutions Lab is a self-service, on-demand environment where you can explore Remote Desktop Manager (RDM) and Privileged Access Management (PAM) hands-on, directly in your browser. No installation, no VM to configure, no infrastructure to touch. Sign in with your Devolutions account, launch a session, and you’re in.

It’s built for evaluation and proof-of-concept scenarios specifically, the kind of testing you don’t want happening anywhere near production.

What you can actually do in there

Once you’re in, the Lab gives you a preconfigured playground to:

  • Simulate real-world access scenarios, the way your team would encounter them day to day.
  • Explore RDM workflows — connections, credentials, centralized management — without setup overhead.
  • Evaluate PAM concepts, including identity and permission management.
  • Test secure access across different types of resources, knowing nothing you do touches your own systems.
  • Follow guided tutorials at your own pace, if you’d rather learn as you go than wing it.

Basically, it’s a way to answer “does this actually work the way we need it to?” before you commit to anything.

How a session works

Each Lab session runs on a timer. You can pause and pick it back up whenever you want, as long as the timer hasn’t run out. Once it does, the environment resets automatically.

That reset isn’t a limitation, it’s the point. It means the Lab stays isolated and consistent every time you or anyone else launches a new session, and you’re free to break things, try weird edge cases, or run through the same scenario twice without worrying about cleanup.

Getting started

Ready to poke around? Head to the Devolutions Lab, sign in with your Devolutions account, and launch a free on-demand session. No setup, no risk to your infrastructure: just hands-on learning through real use cases.