Mozilla creates dedicated enterprise add-on channel for managed Firefox deployments

Mozilla will launch an enterprise add-on channel on addons.mozilla.org (AMO) on December 1, 2026, creating a parallel submission path for browser extensions deployed through Firefox enterprise policies rather than discovered by individual users. These enterprise add-ons—used for security tools, data loss prevention, identity management, and internal productivity—will be marked via the admin_install_only: true manifest key and will not appear on public AMO pages.

The change establishes distinct review policies for enterprise extensions, reducing reviewer load on consumer submissions while maintaining Mozilla's Acceptable Use Policy. All developers must accept an updated Firefox Add-on Distribution Agreement to continue using AMO. IT administrators require no operational changes; deployment through existing Firefox enterprise policies continues unchanged.

Enterprise channel mechanics and manifest changes

• Manifest declaration: Enterprise add-ons must set browser_specific_settings.gecko.admin_install_only to true in their manifest to qualify for the enterprise channel.
• Channel isolation: Versions submitted through the enterprise channel are restricted to that channel and will not be distributed through AMO public listings or other Mozilla channels.
• Review scope reduction: Enterprise add-ons receive lighter manual review under a limited policy set, freeing reviewer resources for consumer-facing extensions.
• Deployment mechanism unchanged: Extensions are still installed via Firefox enterprise policies; the channel change affects only how they enter Mozilla's distribution pipeline.

Why it matters

For organizations managing Firefox at scale, the dedicated channel promises faster security patch propagation by reducing review bottlenecks that previously treated enterprise and consumer add-ons identically. The manifest-based self-declaration model may influence how other open-source browser vendors structure their own enterprise extension workflows, particularly as Chromium-based alternatives already maintain separate enterprise policy systems.