Manage every beta release in Jira

When experimental features roll out, admins are often the last to know—and the first to deal with surprises. Until now, Jira Labs features have been toggled on or off by individual users, leaving admins with little visibility into what’s live across their site. The new Beta Features Management page brings all of that control into one governed, admin-owned surface, so you can confidently decide which betas your organization sees, and when.

How it works

See every beta in one place
Instead of hunting through Jira Labs per user, admins now have a single page in Jira Admin Settings that lists all available beta features for their site. Each beta includes a clear name, description, and context, so you can quickly understand what it does before you flip the switch. No more guessing which experimental experiences are floating around in different parts of Jira – everything is visible, searchable, and managed centrally.

Roll out betas on your terms
From the Beta Features Management page, admins can enable or disable each beta feature for the entire site with one toggle. When you turn a beta on, it’s consistently applied for every user; when you turn it off, it’s off for everyone. That means fewer “Why did my Jira suddenly change?” tickets, fewer surprises for teams, and a more predictable path to adopting new capabilities. You stay in control of when and how changes land across your organization.

Keep your site safe by default
By moving beta controls from end users to admins, Jira makes your environment safer and easier to support. Experimental features no longer appear unexpectedly for individual users, reducing confusion and change fatigue. Instead, admins can review each beta, assess the impact, and choose what to pilot with which teams. With one managed page for all betas, you get a governed way to experiment with new Jira capabilities – without sacrificing stability or consistency for your users.