Rocket.Chat

Release 8.8.0-rc.0

Release Date: August 20, 2026

Support Window: Supported until February 28, 2027

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Added a workspace setting that forces end-to-end encryption on private rooms. With Force end-to-end encryption on private rooms enabled under Administration > Workspace > End-to-end encryption, every newly created private room is encrypted and the encryption toggle in the create-channel and create-team dialogs is locked on. Attempts to create an unencrypted private room are rejected, and creating a discussion under an unencrypted private parent is refused with guidance to make the parent public or turn encryption on. Public rooms are unaffected, and federated rooms are exempt because federation does not support end-to-end encryption. (#41095)

• Added status visibility, letting users hide their presence and status message from specific people. Pick who cannot see your status from the user menu in the top navigation bar or from the status fields in My Account > Profile. Everyone on that list sees you as offline, indistinguishable from someone who is genuinely offline, and you can lift the block at any time. Changes apply live without a reload, and hidden status is also left out of user lookups and search results. (#41747)

• Added classification banners to rooms managed by Attribute Based Access Control. Admins can describe US Government-style classification markings in a new JSON setting under Administration > Workspace > General > Attribute Based Access Control, covering levels, special access programs, releasability and colors. Every member of a room whose attributes match a marking sees a colored classification banner above the room header. (#41307)

• Added an Import IdP metadata action to the SAML settings. Admins can point it at their identity provider's metadata URL under Administration > Workspace > SAML and review the parsed certificate, entry point and IDP SLO redirect URL, plus identifier format on Enterprise, before the values are prefilled into the settings form. (#41481)

• Added SAML sign-in through the system browser for the mobile and desktop apps. Users complete SAML authentication in their system browser instead of an embedded view, so an existing identity provider session is reused and the app is handed the session back automatically. Providers are still configured under Administration > Workspace > SAML, and the public login services response now carries the SAML service details the native clients need. (#41788)

• Announced the deprecation of LDAP and SAML on workspaces without a Premium plan. Both authentication methods keep working in 8.8.0. From 9.0.0 they will require a license that includes the ldap-enterprise or saml-enterprise module. The notice appears under Administration > Workspace > LDAP > Connection and Administration > Workspace > SAML > Connection, and the server logs a warning each time an unlicensed workspace authenticates someone through either method. Workspaces that authenticate through LDAP or SAML without a Premium plan should arrange a license that includes the matching module before upgrading to 9.0.0. (#41642)

• Added per-client rate limiting to password reset requests sent from the login screen's Forgot password form, matching the throttling already applied to the equivalent REST request, so repeated attempts no longer send an unbounded number of reset emails. Imports from a public file URL now check the target host against the allowlist under Administration > Workspace > General > SSRF protection, so an import pointed at an internal address is rejected unless that host is allowlisted. (#41699, #41749)

• Fixed logging out through POST /v1/logout leaving the session recorded as active, which left stale entries in My Account > Device Management and in the admin device management list. Room access checks no longer raise an error when they run for a caller without a resolved identity, such as an unauthenticated or partly initialized session, so those requests are allowed or denied on their merits. (#41573, #41744)

• Fixed special characters in a visitor's name not being escaped in the message preview of the Omnichannel queue side panel, where they could be read as markup instead of shown as text. (#41595)

• Included an undisclosed security hotfix covering thread message retrieval and real-time notification subscriptions. It applies as soon as the workspace is upgraded, with no configuration change. Details are published on the security fixes and updates page. (#41814)

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Turned the draft message indicator on for everyone. Rooms holding an unsent message are marked in the sidebar and in the side panel, and unsent thread replies are kept per thread and marked in the Threads list. Drafts survive switching rooms and reloading. The Drafts in sidebar option is gone from My Account > Feature Preview because the indicator is now always on. (#41355)

• Added paged reply loading to the Threads panel. Replies now arrive a page at a time as you scroll in either direction instead of all at once, so long threads open quickly, and dragging the thread scrollbar keeps pulling in pages. Opening a link to a single reply loads the replies around it and scrolls straight to that message. A thread whose first message was deleted shows a removed-message placeholder instead of an empty row, and a thread whose reply was edited on a workspace that keeps message history shows its first message again. (#40998, #41672, #41705, #41737, #41484)

• Fixed thread replies keeping the single sent checkmark after everyone had read the thread, switching to the double viewed checkmark only once someone posted in that thread again. Read receipts appear when Show Read Receipts is enabled under Administration > Workspace > Message > Read receipts. (#41707)

• Screen sharing for voice calls is now generally available. Users can join internal calls without a working microphone and still use screen sharing. When no microphone is found or access is denied, the permission dialog offers to call, accept, or continue without a mic instead of blocking the call. Users can enable the microphone later from the call widget. Screen share, hold, and transfer controls now appear only when the ongoing call supports them instead of being shown as disabled. Screenshare setting is no longer a requirement for in-room view. (#41837, #41416)

• Recorded incoming SIP calls that were diverted before reaching the workspace as transferred calls, so the call history shows who diverted them, and preserved the caller name carried by the SIP integration. Screen-share negotiation failures and stream identification are handled more reliably during Team voice calls.  (#40560, #41372, #41651, #41654)

• Fixed federated conversations failing between servers. Contacting a user on another homeserver for the first time now opens the conversation instead of erroring, and loading older history, image thumbnails, message paging and accepting an invitation from another homeserver all succeed again. Workspaces with native federation enabled under Administration > Workspace > Federation pick this up on upgrade, with no configuration change. (#41689, #41717)

• Fixed the reply count and last-activity time on a discussion disagreeing with what members see inside it. System messages hidden globally or hidden on that discussion are no longer counted, the parent message's counter and timestamp stay in step with the discussion, and the Hide system messages option in the room's edit panel now explains that hidden messages are not counted. Existing discussions pick up corrected values as new messages arrive. (#41673, #41702)

• Fixed the message list jumping to the newest message when you leave a room and come back instead of restoring where you were reading. Choosing Jump to message on a result from another room now opens that room and scrolls to the message. (#41805, #41711)

• Fixed the mention, slash command and emoji suggestion popups staying open after the composer text changed without typing, for example after canceling the edit of a message that contains a mention. (#41664)

• Fixed very long messages losing their line breaks in the message list, thread previews, quoted messages and the moderation and Omnichannel history views once they passed the workspace's maximum parse length. With Use Real Name enabled under Administration > Workspace > Layout > User Interface, the list of people who reacted to a message shows real names instead of usernames or blank rows. (#41631, #41574)

• Fixed an idle user being set back to Online after a connection drop, network change or server restart. Presence now follows the last real interaction with the app, so someone who has gone Away no longer looks available to everyone else after reconnecting. (#41585)

• Fixed room search failing for visitors who are not logged in on workspaces with Allow Anonymous Read enabled under Administration > Workspace > Accounts. Those visitors can search from the sidebar again, and search for logged-in users is unchanged. (#41876, #41843)

• Fixed editing an existing Omnichannel tag failing with an invalid response error. Creating new tags was never affected. (#41504)

• Fixed Omnichannel business hours configured as 00:00 to 23:59 dropping to closed for the whole 23:59 minute each day, which left agents unable to become available and showed the offline form in the Livechat widget. A business hour now stays open until the end of its finish minute, and no reconfiguration is required. (#41784)

• Deprecated the conditions entry of the selector parameter on the department and visitor autocomplete lookups behind the Omnichannel search fields. Requests that still send it keep working and record a deprecation warning in the workspace logs, so integrations should move to the plain selector fields. (#41766)

• Fixed issues with message deep links (?msg=) when opening older messages. Deep links no longer cause repeated room reloads or leave public rooms blank for anonymous readers when anonymous read access is enabled. (#41499, #41811)

• Fixed excessive message history loading when opening contextual bars on small screens. Opening a thread or other contextual bar no longer loads the entire room history or its attachments while the message list is hidden. (#41454)

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Added a native Model Context Protocol (MCP) server in alpha. Admins can expose an MCP endpoint so external AI clients call a curated set of workspace tools. Two new controls in the AI Center administration area turn the endpoint on and switch it from the minimal curated tool set to the extended one, and both are off by default. Access also requires a license that includes the AI add-on and the new access-mcp permission. The capability ships in alpha. (#41082)

• Added REST endpoints for the two-factor, audit, custom OAuth, thread-read and push-test flows that previously existed only as realtime methods. Account two-factor setup, the admin Audit area, the admin OAuth services page, message sending, thread reading and the admin push test now travel over REST, with the same screens and results for users and admins. The audit endpoints need a license that includes auditing. Enabling or validating an authenticator app under My Account > Security now asks for an existing second factor first. Integrations still calling the replaced realtime methods keep working until 9.0.0 but log a deprecation warning. (#40734, #40736, #40737, #41593, #40675)

• Added an optional fromTs query parameter to chat.syncMessages that bounds the sync window and has to be sent together with lastUpdate. Combining it with cursor pagination is rejected instead of quietly ignored, which makes the endpoint a full replacement for the deprecated realtime missed-messages method. (#41715)

• Validated request bodies against a declared schema on the channel, group, session, license and role endpoints, which now answer a rejected or failing request with a consistent failure payload carrying the error type instead of an unhandled server error. Paths, parameters, responses and permission checks are unchanged, so well-formed requests see no difference, but a caller that relied on a loosely validated body may now get a validation failure. (#41415, #41422, #41632, #41635)

• Changed the default Apps-Engine runtime from Deno to Node.js. Apps now run on the Node.js backend unless the environment variable APPS_ENGINE_RUNTIME_BACKEND is set to deno, which restores the previous behavior. Installing and managing apps remain unchanged, and app developers should expect the Node.js runtime unless that variable is set. (#41474)

• Fixed app action buttons not reaching users with the required role. Role filters now accept role name as well as role _id and support room-scoped roles, including owner, moderator, leader, and custom room roles. Room-scoped roles are matched against the current room so filtered buttons appear in the message and room action menus for the intended users. (#41765, #41777)

• Consolidated the Apps Engine accessor layer, server orchestrator and object converters internally. Apps keep installing, running and notifying users exactly as before, the documented accessor contracts are unchanged, and no app code change is required. A notification regression introduced during the work was fixed in the same series. (#41376, #41377, #41378, #41171, #41738, #38357, #41205)

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Replaced the remaining first-generation sidebar and side panel components with their current versions, keeping the same look and behavior, and fixed the sidebar not scrolling when the room list is taller than the window, so rooms below the fold can be reached again. (#41498, #41683, #41674, #41815)

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Stopped expected, client-safe errors being reported as exceptions to the channel selected in Administration > Workspace > Logs > Log Exceptions to Channel when Log Level is set to Debug. Admins watching that channel now see only genuine unexpected exceptions, so routine validation failures stop creating noise. (#41795)

• Fixed dismissing a banner stored on your own user record, such as the new-version notice shown across the top of the workspace, failing with a banner-not-found error. Those banners are now marked as read and stay dismissed, while dismissing a banner that genuinely does not exist still fails. (#41755)

• Added missing German translations. (#41502)

For more detailed information, check our GitHub release page.

Release 8.7.0

Release Date: August 6, 2026

Support Window: Supported until February 31, 2027

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Added phishing-resistant MFA and a modern server-side OAuth flow. OAuth authentication now uses CSRF protection, state validation, and PKCE, reducing browser exposure to token theft. The new unauthenticated REST endpoints POST /api/v1/loginCode.redeem, POST /api/v1/twoFactorChallenges.sendEmailCode, and POST /api/v1/twoFactorChallenges.verifyChallenge support OAuth sign-in completion and email or TOTP challenges. Admins can enable the flow with Accounts_OAuth_Use_Modern_Flow in Manage → Workspace → Settings → OAuth. (#40721, #41492)

• Added FIPS 140-3 compliant Docker images. Workspaces can now run Rocket.Chat in FIPS 140-3 compliant mode using dedicated FIPS Docker images for the monolith and all microservices, published as tags on Docker Hub. Running in FIPS mode requires a license that includes the new fips add-on, and FIPS status is reported in server logs and workspace statistics. (#39324, #41486)

• Hardened permission enforcement for REST endpoints. Generating a login token for another user through users.createToken now requires the user-generate-access-token permission. The channels.convertToTeam endpoint now applies the required room permission checks whether the channel is identified by ID or name, and teams.create applies the same checks when creating a team from an existing room. Callers without the required permissions now receive an authorization error where the requests previously succeeded. (#40768, #41206)

• Two concurrent logins can no longer consume the same CAS login token. Revoking a room invite no longer emits duplicate removal notifications, and users can no longer delete integrations they don't own. (#41174)

• Fixed a race condition when creating an encrypted room that could leave messages permanently undecryptable with an "incorrect encryption key" error when several members opened the room at the same time. (#41169)

• Fixed SAML Single Logout so logout responses echo the RelayState value received in the request, as the SAML specification requires. Identity providers that validate RelayState now complete sign-out without errors. (#41145)

• Fixed vulnerabilities that could allow authentication bypass in SAML single sign-on and unauthorized impersonation through forged ephemeral messages. (#41069, #41233)

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Introduced Unified AI Search as an opt-in feature preview, adding semantic message search and grounded AI-generated answers to the global search bar for more accurate natural language search across rooms. (#40890, #41464, #41434)

• Added GitHub-style tables and horizontal rules to message formatting. Messages now support pipe-delimited tables with optional column alignment and inline formatting inside cells, plus horizontal rules typed as a line of three or more dashes. Clients that do not yet support a new block show the original markup instead of dropping content, and code blocks no longer break when a line inside them ends with a backtick. (#41109, #41113, #41110, #41312)

• Added a persistent audio player that continues across room navigation. Playing an audio attachment now continues when you switch rooms or close the conversation, and a Now Playing card at the top of the sidebar offers play/pause, seek, playback speed (1x/1.5x/2x), and a shortcut back to the source conversation. (#41120)

• Replaced the bundled emojione set with native Unicode emojis. Rocket.Chat now renders native Unicode emojis, increasing the number of available emojis in the picker and in messages, while legacy emojione shortnames in existing messages keep rendering through a compatibility map. Follow-up fixes restore combined emojis and regional flags that briefly displayed incorrectly. (#39411, #41305, #41441)

• Added relative time to the date columns in the Omnichannel Contact Center. The Last Chat column in the contacts list and the Started At and Last Message columns in the chats list now show how recent each conversation is alongside the formatted date. (#41204)

• Fixed custom Omnichannel business hours so their department links survive daylight saving time changes and server restarts. Agents removed from a linked department now have their availability recomputed immediately instead of keeping a stale schedule. (#41158, #41164)

• Fixed the "user left" system message so it appears in its correct chronological position after an Omnichannel conversation is forwarded to another agent or department. (#41480)

• Fixed editing or deleting a message in a Matrix-federated room corrupting the room's federation event tree, which previously stopped all subsequent messages in that room from syncing between servers. The fix prevents new corruption only: rooms already affected need a separate one-time repair. (#41046)

• Fixed voice calls failing when you navigate between rooms during the initial connection, and prevented VoIP license or permission changes from reloading the web app and interrupting active calls. (#41044, #41200)

• Improved keyboard accessibility: the Display menu's radio buttons and checkboxes can now be toggled with the keyboard, and the room Members list supports keyboard navigation. (#41089, #41122)

• Fixed a batch of interface issues: the cursor now lands correctly after inserting a mention, quote attachments show a visible link to the original message, emoji picker buttons respond correctly to clicks, video attachment controls are clickable again on Chromium 150, usernames align correctly in the Read Receipts list, dates no longer show one day early for users in negative UTC-offset timezones, your own account no longer appears twice in navbar search, Composer actions are disabled when previewing a public channel without joining, and non-renderable image formats are rejected as avatars. (#41074, #41091, #41152, #41195, #41199, #41202, #41223, #41229, #41230)

• Restored the "Away" presence status option to the user menu’s quick status options. (#41414)

• Fixed an issue where audio attachments could not move to a different playback position using the progress slider. (#41588)

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Added an alternative Node.js runtime backend for the Apps Engine. Workspace admins can now run Rocket.Chat apps on a Node.js-based runtime instead of the default Deno subprocess by setting the APPS_ENGINE_RUNTIME_BACKEND environment variable to node. Apps behave the same under either backend. (#41019, #41125, #41149)

• Added REST endpoints for users.verifyEmail, cloud.connectWorkspace, integrations.clearHistory, and integrations.replayOutgoing that replace the equivalent DDP method calls. The corresponding DDP methods now log deprecation warnings and are scheduled for removal in 9.0.0. Avatar uploads through POST /v1/users.setAvatar now support an optional service field that preserves the original OAuth provider name.(#40728)

• Enabled the web client to push the logged-in user's roles to the Rocket.Chat desktop app whenever they change, so the desktop client can show version-support warnings only to relevant roles such as admins. Older desktop builds fall back to their own role lookup. (#41056)

• Fixed apps failing with "Module not found" errors in some cases after a workspace upgrade, and made the apps runtime write its configuration to the system temp directory so app startup no longer fails with EACCES errors in Docker deployments running under a custom UID. Type definitions for federated users and UIKit interaction responses were also corrected for app developers. (#40947, #41338, #41304, #41310)

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Improved performance and query efficiency: navbar search returns results faster and can read from secondary database replicas when available, the engagement dashboard no longer loads unnecessary data into memory on startup, and pagination on rooms.bannedUsers and Omnichannel department listings honors the offset parameter again. (#41101, #41207, #41402)

• Upgraded the web client's rendering baseline to React 19 without changing user-facing functionality. Fixed URL preview embeds flickering when new messages or reactions arrived in a room. (#40796, #41299)

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Added XMPP federation bridge support. Workspaces with the required license can now connect Rocket.Chat rooms to XMPP networks through the federation service. Administrators can configure the bridge under Manage → Workspace → Settings → Federation after enabling native federation. (#40758)

• Stopped all outbound connections for licensed airgapped workspaces. Workspaces with an offline license no longer attempt outbound connections to Rocket.Chat Cloud, the Push Gateway, or other cloud services, keeping air-gapped deployments compliant at the source. The server now correctly applies the newest valid license at startup, including licenses provided through ROCKETCHAT_LICENSE . The setup wizard no longer forces the registration step after an upgrade when the OVERWRITE_SETTING_Show_Setup_Wizard=completed  environment variable is set. (#41148, #41472, #41254)

• Added a Manage License flow in Administration > Subscription where admins can preview, apply, and remove a workspace license. The pasted license is validated with the new /licenses.validate endpoint before it is applied, and invalid values are rejected with the specific validation results shown instead of being saved. (#40916, #41306)

• Improved admin settings validation and reliability: settings that hold JSON now validate inline in the editor and block save while the value is malformed, saving a password-policy Maximum Length lower than the Minimum Length is now rejected with an explanatory error, and re-enabling the Enable Push setting no longer crashes the server. (#41142, #41173, #41341)

• Fixed an issue where logging out the current device from the Device Management view showed an error even though the logout succeeded. Added a current field to the /sessions.list endpoint to identify which session belongs to the device making the request. (#40351)

• Improved the Slack importer so shared files arrive as native attachments with image previews instead of raw URLs. Imported file messages stay hidden until an admin clicks Download Pending Files, and failed downloads are counted as retryable errors instead of being saved as the file's content. (#41285)

• Fixed LDAP synchronization issues: channel sync now completes the full channel map even when one mapped channel is missing, users matched by email now merge into their existing account instead of failing with a "Username already exists" error, and an invalid search filter now logs an error instead of crashing the server during login or sync. (#41168, #41279, #41373)

• Restored the customFields property on the admin room details endpoint (rooms.adminRooms.getRoom), so custom fields display again in the admin room detail view. (#41112)

For more detailed information, check our GitHub release page.

Release 8.6.0

Release Date: July 3, 2026
Support Window: Supported until January 31, 2026

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Added support for Virtru as an external attribute store for ABAC. When the Policy Decision Point (PDP) is set to Virtru on the Attribute Based Access Control admin panel, a new Attribute store setting selects where assignable room attributes come from. With Virtru as the store, attributes are managed externally and limited to those the acting admin possesses, and the Room Attributes tab is hidden. Switching the attribute store permanently clears all existing room attribute assignments; no users are removed and rooms remain private. Changing the PDP requires confirmation, and switching it back to local also resets the attribute store to local. (#40634, #40826)  

• Hardened Apple sign-in by validating the identity token issuer, expiry, and audience, and removed the email fallback that could enable account takeover. Deleting an uploaded file now requires an authenticated caller with delete permission. (#40889)

• Added an authorization check to the POST /api/v1/fingerprint endpoint so an arbitrary authenticated user can no longer deregister the workspace from Rocket.Chat Cloud. Unauthorized callers now receive a permission error. (#40706)

• Escaped HTML in message exports and emailed data downloads so exported transcripts cannot carry executable markup. (#40802)

• Hardened the Apps Engine app manager and package parser against prototype pollution by building internal objects with a null prototype. (#40763)

• Fixed an issue where temporary LDAP or Active Directory account lockouts could incorrectly deactivate users in Rocket.Chat during synchronization.(#40842)  

• Redirected expired sessions to the login page instead of leaving users on a stale screen, restoring the expected re-authentication prompt. (#40849)

• Fixed users.sendConfirmationEmail rejecting unauthenticated requests, unverified users can now resend their verification email from the login screen. (#40702)

• Only users with Impersonate Other Users permission can now be used in the Post as field when creating new incoming integrations. (#41017)

• Fixed PDF downloads from the PDF Viewer in encrypted rooms on the desktop app, preserving the original file format and filename. (#40517)

• Fixed an SSRF-related issue that could prevent incoming integrations from reaching internal network hosts. (#41057)

• Fixed an issue where personal access tokens configured to ignore two-factor authentication were incorrectly rejected by API endpoints requiring two-factor authentication. (#41065)

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Pop out a voice call into a separate window. During a voice call you can now move the call widget into a separate floating window so it stays visible while you navigate the rest of the workspace. The window keeps all existing call controls and returns to the main widget when closed. (#40202)  

• Added LibreTranslate as a message auto-translation provider, alongside Google, DeepL, and Microsoft. (#40900)

• Added a POST /api/v1/rooms.join endpoint that lets a user join any type of room, including discussions. This also fixes the Discussion Join button failing with error-room-not-found. (#40996)

• Enabled automatic message translation for users who joined rooms before choosing a language preference under My Account > Preferences > Localization. (#40992)

• Fixed voice calls failing when accepted from the mobile device lock screen with the app already open. (#40422)

• Direct messages with deactivated users are now marked read-only, preventing sending messages to inactive users. (#40767)

• Fixed an issue that could prevent bots from being assigned to conversations after reaching the maximum simultaneous chats limit configured for agents, causing some chats to remain unassigned.. (#40635)

• Improved attachment handling by adding dedicated accessibility alternative text for images, restoring attachment descriptions and translation support, and fixing crashes caused by attachments with non-text field values. (#40839, #40860, #39273)  

• Fixed message search crashing the workspace when an invalid regular expression is used, the search now returns an error instead. (#40788)

• Fixed room opening after a network reconnection so a false "Room not found" message no longer appears for rooms you can access. (#40991)

• Stopped the client from marking a room as read when you have no active subscription to it, removing spurious errors on unserved Omnichannel rooms. (#40719)

• Fixed thread panel scroll and reply behavior: threads now scroll to the latest message after a reply, the message list no longer jumps as the composer grows, and replies reappear after reload in threads with more than fifty messages. (#40956, #41007, #40913)

• Fixed jump-to-message behavior so the main channel scrolls to the correct message when opening a thread message link after a page refresh. (#40953) .

• Fixed UI stability issues in room and team views: the contextual bar now shows an error fallback, the code editor unmounts cleanly, video conference users are not registered in embedded layouts, team channels are now sorted correctly, and the channel selection modal loads when removing a team member. (#40970, #40902, #40982, #40955, #40857)

• Fixed a persistent history bar remaining visible in user search and a large blank area appearing below the last item on Account settings.(fuselage #1982, fuselage #1980).

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Introduced a unified presence sync engine that resolves a user's online status with a priority-based claim system, status expiration, and previous-state restore. As part of this change, Away was removed from the user menu’s built-in presence options and can no longer be selected directly from that menu. The users REST endpoint and Apps Engine user objects expose the resulting status. (#40274, #40469, #40846)

• Exposed isFederated and federation fields on Apps Engine room and user objects so apps can branch logic on whether a room or user is federated. (#40791)

• Added a POST /api/v1/custom-sounds.delete endpoint to remove a custom sound by _id, replacing the deprecated deleteCustomSound DDP method. (#40532)

• Extended several REST endpoints to mirror their deprecated DDP equivalents (chat.delete fileId, spotlight, users.setPreferences utcOffset) and added e2e.requestSubscriptionKeys, im.blockUser, and settings POST endpoints. Deprecated DDP methods now log a warning and remain until 9.0.0. (#40711, #40724, #40659, #40704, #40654, #40981)

• Fixed a server crash when an installed Marketplace app is updated twice in quick succession. (#41009)

• Fixed an issue where editing or deleting a message in a federated room caused subsequent messages to stop syncing between servers. This fix prevents future synchronization issues but does not repair federated rooms that were previously affected. (#41046)

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Fixed S3-compatible file uploads failing when the Region is empty or the Bucket URL omits a scheme. (#40759)

• Sped up room opening by parallelizing and caching message-history loads, and made navbar search show results faster using cached subscriptions. (#40965, #40954, #40718)

• Virtualized the Discussions list in the contextual bar for smoother scrolling and lower memory use on long lists. (#39394)

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Added Filipino (Tagalog) to the available language options in both the user language preference settings and the default workspace language settings. (#40988)

• Added the workspace hashed URL on the Manage > Workspace deployment card and in server startup logs. (#40685)

• Improved avatar URL validation error messages to preserve the exact URL submitted by the user without additional encoding. (#40980)

For more detailed information, check our GitHub release page.

Release 8.5.0

Release Date: June 10, 2026

Support Window: Supported until June 30, 2026 (LTS - 12 months from release date)

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Autotranslate access hardening — Enforced permission and room-membership checks on the autotranslate.translateMessage Meteor method and REST endpoint before message content is returned. BREAKING: integrations that previously called this endpoint without proper room access now receive a 401 or 403 response and must add the caller to the room. (#40508, #40528)

• OAuth token revocation on deactivation — Deactivating a user via Administration > Workspace > Users or through the users.deactivateIdle and admin deactivate endpoints now revokes the user's OAuth access, refresh, and authorization-code tokens alongside their login tokens, closing a session-persistence gap where deactivated users could still call the API with previously issued OAuth tokens. (#40524, #40496, #40525)

• Visitor token removed from livechat/visitors.info — Stripped the token field from the livechat/visitors.info REST response so visitor tokens are no longer returned on lookup. BREAKING: integrations that read token from this response must obtain it through the existing visitor-creation flow instead. (#40501)

• Added URL sanitization to inline images in rendered messages, blocking unsafe schemes such as javascript: from loading as images. (#40613)

• Hardened SAML SSO and file uploads as a bundled set of imported security fixes: the SAML service provider validates signatures and envelopes more strictly during SP-initiated logout, the file upload pipeline rechecks MIME and ownership before persisting, SAML and CAS login handlers now fail closed on parse errors, and the OAuth server's model layer enforces token scoping. (#40405)

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Sidebar drafts group — Added a Drafts group to the top of the sidebar that surfaces rooms with an unsent composer draft when the Drafts feature preview is enabled under Account > Preferences > Feature Preview. Selecting a draft room restores the composer text so users can resume writing. (#38225) 

• Message list virtualization — Virtualized the channel view's message list, reducing memory and rendering cost in long conversations and threads. Follow-up fixes ensure that jumping to the latest message scrolls correctly, thread panel closes correctly when a message is opened from search, the thread parent message keeps its edited indicator, and thread content no longer disappears after jumping to recent messages. (#40105, #40624, #40623, #40622, #39859, #40063) 

• Voice call fixes — Restored the Open in Room button on the media-call widget when a screen is being shared, stopped the error toast that appeared when cancelling a screen-share request, kept the call service stable when a Drachtio (SIP) connection drops mid-call, and re-enabled rejection of users attempting to call themselves. (#40331, #40330, #40197, #40229) 

• Accessibility improvements — Extended keyboard navigation to every message selectable for export, added inline errors to the Enter E2EE password modal and the TOTP code modal, and corrected required-field, label, and error-binding wiring on non-admin form inputs for assistive-tech compatibility. (#40256, #37146, #36350, #37049) 

• Audio and video message buttons are no longer disabled while typing in the composer, allowing users to start recordings even after drafting text. (#40334)

• Hid the Delete all closed chats button from Contact Center for users who lack the Remove All Closed Omnichannel Rooms permission, and restored room-scoped custom fields to display in the Room Information sidebar.(#40492, #40325)

• Fixed several user-visible issues: users.presence accepts comma-separated IDs again, file-upload signed URLs fall back to the default expiry when the configured value is below the safe threshold, message timestamps respect the workspace timezone and relative-time previews render correctly, embedded mode no longer flashes "Channel Not Joined" on entry, the message list survives portal and iframe renders, and an invalid Message_DateFormat setting falls back to long-date instead of crashing the message list. (#40513, #40456, #40420, #40100, #40391, #40393, #40190) 

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Added REST endpoints for creating and updating custom sounds with multipart uploads, file-type, and size validation, deprecated the legacy insertOrUpdateSound and uploadCustomSound Meteor methods with a runtime warning, and fixed the Test button under Account > Notifications Preferences so it plays the default sound for the Default preference. (#39617, #39725, #40335)

• Added a freeSwitchExtension query parameter to the users.info REST endpoint and a matching IUserRead accessor on the Apps Engine user bridge so integrators can look up a Rocket.Chat user by FreeSwitch extension. (#40612, #40604)

• Exposed the originating room on additional UIKit interaction contexts — action buttons, modals, and view-close — so app developers can read the room directly from the interaction payload without an extra lookup. (#39858)

• Moved app-management code from @rocket.chat/apps-engine into a new internal @rocket.chat/apps package without changing the public Apps Engine surface, and fixed UIKit action buttons in the User Dropdown context so they render under the correct menu group. (#40343, #40448)

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Per-room messages text index — Added the USE_ROOM_SEARCH_INDEX environment variable that scopes the MongoDB messages text index by room, improving search performance and reducing MongoDB resource usage in large databases. It is intended for workspaces that do not use global search.. (#40397) 

• Tunable markdown parse length — Added the MESSAGE_MAX_PARSE_LENGTH environment variable to skip server-side markdown parsing for very large messages and reduce CPU usage. (#40306) 

• Bump engine versions — Updated the runtime baseline to Node.js 22.22.3, Meteor 3.4.1, and a refreshed Alpine base image used by the official Docker images. (#40535, #40536, #40389, #40406)

• Cached user records consulted during DDP publication-access checks and invalidated entries on watch.users events, reducing repeated MongoDB queries and ensuring permission updates apply immediately in microservices deployments. (#39667, #40614) 

• Improved Prometheus metrics with additional labels, granularity, and histograms across HTTP, DDP, and queue series. Scrape the /metrics endpoint as before; existing dashboards continue to work, with new series available for finer alerting. (#39857)

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Granular ABAC administration — Added a tabbed ABAC administration page with granular per-tab permissions under Administration > Workspace > ABAC. ABAC-managed rooms now hide announcement and topic edits in the room information panel and automatically drop their attributes when converted to public channels. The Apps Engine bridge exposes abacAttributes to apps through a new secure-fields permission, and the ABAC room sidebar uses a filterable multi-select for easier room lookup. (#40408, #40463, #40341, #40423, #40537, #40499, #40511) 

• Added experimental Use Rocket.Chat SDK admin setting that routes real-time communication through Rocket.Chat's DDP client instead of the default Meteor WebSocket transport. (#40430)

For more detailed information, check our GitHub release page.

Release 8.4.0

Release Date: April 30, 2026

Support Window: Supported until October 31, 2026

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Added validation of the IDP SLO Redirect URL on every SAML Single Logout request, requiring an exact match with the IdP SLO endpoint. (#38994)

• Federated re-invite flow no longer readmits banned users, closing a bypass in the federation subscription sync. (#40114)

• Apps engine logs support ad-hoc redaction to scrub sensitive fields before logs are exposed. (#40096)

• Fixed an access control issue where apps logs endpoints could be accessed by any authenticated user; RBAC checks are now enforced. (#40225)

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Image previews in the composer and files list — Image files now display as thumbnails in the composer before sending and in the files list when browsing shared files. Images under 10 MB show previews; larger files and other types show icons. (#40181)

• Alternative text for images — Add alt text to images before sending. Alt text improves accessibility for screen readers and appears when an image fails to load. (#40075)

• Composer formatting shortcuts — Select text in the composer and press a formatting key (*, _, ~, or `) to automatically wrap the selection with the matching delimiter for bold, italic, strikethrough, or code formatting. (#39393)

• Global keyboard shortcuts — Keyboard shortcuts moved from room scope to a global view. Press Shift+? anywhere in Rocket.Chat to open a modal listing all available keyboard shortcuts. Global shortcuts include Ctrl+K to search channels or users and Ctrl+Escape to mark all messages as read. (#40169)

• Search result announcements in the contextual bar — Screen readers now announce the number of search results when searching for discussions, files, or members in the contextual bar. (#39847)

• Global search result announcements — Global search results are now announced to screen readers, improving workspace-wide search accessibility. (#40023)

• External IDs for Livechat visitor identification — Match Livechat visitors across external systems by providing one or more external IDs when creating or updating a visitor. Recognize returning visitors from your CRM or helpdesk. (#39535)

• Omnichannel Contact Center date formatting — Chat table dates in the Contact Center are now formatted consistently for readability. (#40025)

• Added a validation that prevents banned users from accepting invite links until unbanned by an administrator. (#40087)

• Fixed an issue where re-inviting a banned user could incorrectly remove their other room subscriptions. (#40061)

• Fixed the Accept new omnichannel requests when the agent is idle setting to exclude agents with offline presence from auto-assignment, ensuring only available agents receive chat assignments. (#39495)

• Fixed read receipts not turning blue once all active users had read a message. (#39246)

• Fixed incorrect colors on attachment drag-and-drop surfaces. (#39890)

• Fixed the "Reply in direct message" action not appearing for users with the create-DM permission. (#40078)

• Fixed a regression with multiple compounding keys pressed in sequence. (#40108)

• Fixed expanded thread view overlapping the navigation bar. (#39892)

• Fixed missing visual feedback when a room mention click errors. (#39985)

• Fixed blank notifications appearing when a voice call ends. (#39741)

• Fixed Livechat not respecting the "accept chats with no agents" setting under certain conditions. (#40175)

• Fixed Livechat visitor emails and phone fields being reordered alphabetically. (#39905)

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Per-integration script transpilation toggle — Each webhook integration now has a Transpile Script with Babel toggle (enabled by default). Disable it per-integration to test scripts without Babel transpilation. Babel will be removed entirely in Rocket.Chat 9.0 — test with scriptTranspile: false before upgrading. (#40160)

• Early call acceptance in media calls — Added support in the media-calls API to accept calls before full session establishment, improving call-flow timing for advanced integrations. (#40141)

• Media calls state endpoints — New media-calls.state and media-calls.stateSignals endpoints expose real-time visibility into active call state for integrations. (#40093)

• User email filtering — users.info and users.list now support an email query parameter for filtering users by email address. (#39989)

• Settings action type extension — POST /api/v1/settings now supports endpoint-based action types, allowing more flexible setting actions. (#39983)

• DDP void methods now correctly return 404 responses instead of hanging, improving the reliability of void method calls in custom integrations. (#40057)

• App actions now respect role filters and i18n translation. (#39868)

• The message updater context is now available to apps. (#39883)

• Presence broadcast disabled status is now surfaced correctly to clients. (#40051)

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Cold storage archiving for read receipts — Automatically archive read receipts from hot storage to cold storage after a specified retention period to reduce database size and improve performance. Configure retention days, archive schedule, and batch size. (#38623)

• Rocket.Chat Docker image slimmed to ~260 MB (-14.7%). (#40128)

• Replaced the @react-aria/i18n barrel import and trimmed a lodash import (-110 KB). (#40110)

• Slimmed barrel imports for react-aria, react-stately, and zod (-799 KB). (#40109)

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• External Policy Decision Point (Virtru ABAC) — Configure an external Policy Decision Point to centralize attribute-based access control decisions using Virtru instead of local ABAC policies. Set Virtru connection credentials, attribute mapping, and sync intervals. (#39845)

• LDAP ABAC settings UI — LDAP attribute synchronization settings for ABAC are now available on the ABAC configuration page, with a Sync Now button for manual synchronization. (#40088)

• LDAP attribute sync for ABAC — The Sync Now endpoint now syncs ABAC attributes from your LDAP directory, keeping user attributes in sync with your identity management system. (#40095)

• Mobile ringing for voice calls — Enable push notifications to ring users on their mobile devices when a voice call is incoming. Works with both iOS and Android Rocket.Chat apps when push services are configured. (#39386)

• Auto Away preference hints — Auto Away notification preferences now include helper text explaining each option. (#40050)

• Avatar URL validation — Inline validation now appears when you enter an invalid URL in avatar settings, helping you correct the URL before saving. (#36656)

• Outlook Calendar action toggle enforcement — The Outlook Calendar integration action now respects the Outlook_Calendar_Enabled toggle. (#39986)

• Custom sounds pagination — The Custom Sounds administration list now supports pagination when the number of sounds exceeds the display limit. (#40113)

• Removed outdated oplog error messages from the Admin Workspace page. (#40066)

• Fixed the Engagement dashboard becoming unresponsive under load. (#40058)

For more detailed information, check our GitHub release page.

Release 8.3.0

Release Date: April 7, 2026

Support Window: Supported until October 31, 2026

To improve security and stability, API endpoints are being updated to enforce stricter input validation. Integrations that send values outside the documented format may start to fail. Please review and update your implementation to avoid disruptions.

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Fixed an issue where GitHub OAuth could fail to retrieve a user’s email address during login or signup.

• Fixed a critical authentication bypass vulnerability where specially crafted access_token query parameters could allow unauthorized access to protected REST API endpoints.

• Fixed an issue where the Federation domain allow list was not enforced correctly, which could allow communication with domains that should have been blocked.

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Enhanced federation collaboration and moderation with user banning and unbanning, a dedicated banned users list and system messages, improved remote profile syncing for names and avatars, and cross-domain read receipts in federated rooms.

• Added screen sharing in voice calls, currently available in beta, to support better team collaboration.

• Added support for uploading multiple files in the message composer, improving the file upload experience.

• Fixed message parsing for ordered lists that start at 0.

• Fixed an issue where Markdown document rendering could ignore line breaks and show \n as plain text instead of line breaks.

• Fixed an issue where agents were not shown an error after reaching the maximum chat limit and trying to take another chat.

• Fixed inconsistent federated username formatting across the UI so usernames no longer appear with an extra @.

• Resolved an issue where existing members could not forward messages into password-protected public channels and would incorrectly see Code required [error-code-required].

• Fixed an issue where Hebrew text could appear as garbled characters in exported PDF files.

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Added OpenAPI documentation and response validation for e2e ,  e2e.fetchMyKeys , commands.get , push.test , e2e.getUsersOfRoomWithoutKey , autotranslate.translateMessage , custom-user-status.list , rooms.favorite , rooms.delete , e2e.updateGroupKey, users.getAvatarSuggestion ,  emoji-custom.create , chat.unfollowMessage , chat.followMessage , chat.starMessage , chat.unStarMessage and more API endpoints .

• Fixed the groups.history API so the inclusive=false query parameter is handled correctly.

• Fixed the livechat/rooms API so the query and fields parameters are applied correctly.

• Expanded the push token registration API to support additional required device and token data, including Apple VoIP push token handling for call notifications.

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Improved federation reliability by adding circuit breakers and timeouts for unresponsive remote servers.

• Storage settings for custom sounds and custom emojis now apply reactively, so changes to storage type and filesystem path take effect immediately without restarting the server.

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Fixed an issue where APNs could still initialize in production mode even when Push_production was set to false, causing certificate errors for development push setups.

• Addressed an issue where users without the Create Public Channels permission could still edit a team and change it from private to public.

• Deprecated the “Allow Anonymous Write” feature in the “Accounts” settings. The feature will be removed in version 9.0.0.

For more detailed information, check out our GitHub release page.

Release 8.2.0

Release Date: March 2, 2026

Support Window: Supported until September 30, 2026

Security and Compliance

Security improvements, authentication changes, data protection, and vulnerability fixes.

• Added SSRF protection by moving URL validation into the server-fetch package, adding built-in safeguards such as internal IP blocking, DNS rebinding protection, IPv6 and port handling, controlled redirect behavior, and an ignoreSsrfValidation option for safe use cases, along with a new workspace setting to allowlist specific domains or IPs and ports.

• Added a new Federation setting with an extra layer of validation to restrict the usage of Federation to only users with a validated email address that matches the configured Federation domain.

• Added rate limiting to verification email resend requests to prevent email spam.

• Resolved a security issue where the users.updateOwnBasicInfo API response exposed the password field and the full services object.

• Fixed a security vulnerability in the Enterprise DDP Streamer service where the Account.login method did not enforce Two Factor Authentication or validate user account status, potentially allowing 2FA bypass and login of deactivated users.

• Addressed an issue where server-side query parameters were not properly validated when queryFields was empty, preventing potential security and data integrity risks.

Messaging and Collaboration

Features and fixes related to messaging, channels, discussions, and communication workflows.

• Standardized username display to include an @ prefix across UI (such as autocomplete options, composer mentions, room member listings, and nicknames), and adjusted surrounding nickname spacing for consistent presentation.

• Fixed an issue that prevented creating a discussion in an encrypted channel when an initial message was added, and ensured the message input is no longer shown when discussions cannot accept a first reply.

• Patched an issue that allowed messages to be sent to archived rooms via the API, ensuring archived rooms no longer accept new messages.

• Addressed an issue where subscriptions to end-to-end encrypted rooms were not being properly decrypted.

• Patched an issue where deleting end-to-end encrypted messages did not remove their associated file attachments.

• Fixed an issue where users could start video conference calls in read-only channels by enforcing standard message permission checks on the video-conference.start endpoint.

Platform and Extensibility

Developer platform, APIs, integrations, and application framework improvements.

• Added multiple file support to Apps-Engine.

• Introduced a new endpoint uploads.delete to delete uploaded files individually.

• Updated OpenAPI documentation generation to support multiple HTTP methods under the same endpoint path, ensuring routes are registered and displayed correctly.

• Fixed an issue where the Apps Engine router did not correctly handle dynamic route parameters, causing requests to endpoints such as webhook/:event to fail.

• Addressed an issue with Apps-Engine where logs were being lost in nested requests.

• Fixed an issue where incoming webhooks did not correctly parse JSON sent in the payload field of application/x-www-form-urlencoded requests, resulting in undefined message fields.

• Fixed an issue with outgoing integrations where the Retry Count field was rejecting numbers and not saving the integration. Retry count is now reliable and the integration saves successfully.

Data, Storage, and Infrastructure

Database, performance, storage, and system-level improvements.

• Updated the minimum supported MongoDB version to 8.0, providing a more stable and predictable support matrix.

• Added MongoDB TTL index to automatically expire statistics documents after 1 year (365 days), capping storage to approximately 70MB regardless of how long the server runs, reducing retained data and storage.

Admin, Configuration, and Workspace Management

Administrative controls, configuration settings, and workspace management improvements.

• Resolved an issue where the “Enterprise plan active” pop-up appeared after every server restart, even when it had already been shown. The issue was caused by a failing POST request to /api/apps/ui.interaction/cloud-announcements-core, which returned a 500 error and prevented the pop-up state from being properly saved. The fix ensures the pop-up behaves as expected and does not reappear unnecessarily after restarts.

• Fixed an issue where agents could be assigned more chats than their configured limit after routing for microservices deployments.

• Resolved an issue where the Contact Manager field could not be cleared via the UI or API, causing existing values to persist even after attempting to remove them.

• Fixed an issue where the /api/v1/audit.settings endpoint did not handle sort parameters correctly, returning a 400 error or ignoring the provided sort field.

• Fixed an issue in the livechat/custom-fields.save endpoint schema where the wrong parameter was validated, ensuring the custom field ID is correctly validated during creation to match the original Meteor method behavior.

Release 8.1.0

Release Date: February 10, 2026

Support Window: Supported until August 31, 2026

What’s new

• Rocket.Chat Voice: Calling and call-forwarding menus now reflect presence changes in real time, making call handling clearer and more reliable. You can jump straight into a direct message from the calling widget for faster follow-ups. On the backend, increased timeout for call activation and customized the “From” number on outgoing external calls via FreeSwitch.

• Strengthened default password security by enabling password policy enforcement out of the box. New installations now apply safer baseline requirements, reducing the risk of weak or easily guessable passwords and improving protection against credential-based attacks. Administrators can still customize the policy as needed to meet organizational security standards.

Bug fixes

• Fixed several calling and notification issues to improve reliability and user experience. This includes cleaner message block layouts, more consistent call reactions, better handling when microphones or speakers are unavailable, and fixes for incorrect call sounds and premature audio playback. Call setup is now more robust, with improved ICE handling and longer activation timeouts to prevent failed or interrupted calls.

• Fixed an issue where users with custom administrative roles on Commercial workspaces saw an incorrect “premium capability” upgrade pop-up when accessing Engagement, Device Management, or Workspace statistics. The workspace registration and subscription status now display correctly for non-Admin roles without requiring privileged settings access.

• Fixed an issue where uploading large files to S3 could cause excessive CPU and memory usage, leading to server crashes and failed uploads. Large file uploads are now handled more efficiently, preventing out-of-memory errors and improving stability when using S3 as the file storage backend.

• Reduced memory usage during file uploads handled by the Apps Engine. File contents are now streamed to a temporary file instead of being fully serialized and transferred in memory for the IPreFileUpload event. This eliminates multiple in-memory copies of large files, avoids base64 encoding overhead, reduces pressure on inter-process communication, and significantly improves stability and performance for large uploads.

• Fixed an issue in the /api/v1/livechat/room.forward endpoint where rooms could appear to transfer successfully even when chat limits were reached. The API no longer returns a successful response or posts a “chat transferred” message unless the transfer actually completes.

• Fixed an issue where direct messages were incorrectly counted toward the maximum rooms per guest limit. Guest room limits are now calculated correctly and no longer include DMs when enforcing license constraints.

• Resolved an issue where livechat agent chat limits were not consistently enforced, allowing some agents to receive more concurrent chats than their configured limit. Agent routing now correctly respects the maximum active chat setting across all assignment and transfer scenarios.

• Fixed an issue where changes to username formatting made via OAuth or LDAP were not reflected in the Direct Messages sidebar. Updated name formats now display correctly across the UI, including existing DM lists.

• Fixed an issue where blacklisted file types could bypass upload restrictions by renaming files during the upload dialog. File validation now enforces blacklist rules based on the final filename and content, preventing restricted file types from being uploaded even if they are renamed mid-upload.

• Patched a regression in v7.10.0 where leaving the SAML Custom Authn Context setting empty in the UI was ignored by the backend. The <RequestedAuthnContext> tag is now correctly omitted from SAML requests when the field is left empty, restoring expected behavior and preventing authentication issues in ADFS and hybrid authentication setups.

• Resolved an issue where saving webhooks triggered a Babel module script error in the network logs, even when no script was defined. Webhooks can now be saved without generating client-side errors, improving reliability and reducing noise during configuration.

• Fixed an issue where the Workspace Info page could display mismatched Server Version and Deployment Version values after an update. Both fields now correctly reflect the currently running version following a workspace upgrade.

• Fixed an issue where sensitive credentials could be exposed in plain text within Security Logs. Credentials are no longer logged in readable form, reducing the risk of accidental exposure or misuse and aligning logging behavior with security best practices.

• Addressed an issue with file uploads in rooms where uploaded files were added to the list of room files, even if the files were not sent to the room. Now the list of file uploads displays confirmed files that are sent to rooms.

• Fixes an issue where a deleted user’s files persisted. Now when a user is deleted, all file attachments (including messages with multiple attachments) and their thumbnails are reliably removed.

• Added support for multiple file attachments in a single email to the Omnichannel Email Inboxes feature.

• Resolved an issue where incorrect values for the MONGO_OPTIONS environment variable caused the application to crash. Now improved error handling with clear descriptions helps to quickly identify and fix configuration issues.

• Fixes an issue in the user bio UI window where lines would break in the middle of links. Now links are displayed properly, improving readability.

• Addressed an issue with the /api/v1/livechat/messages endpoint where a new visitor couldn’t send a message. Now the endpoint accepts messages from new users.

• Fixed an issue where repeated calls to setUserPreferences could be triggered across multiple open tabs, leading to excessive API requests, high resource usage, and browser slowdowns or freezes. Preference updates are now handled more efficiently to prevent request flooding during login and logout scenarios.

Release 8.0.0

Release Date: January 12, 2026

Support Window: Supported until June 31, 2026

Breaking changes

• ⚠️ Discontinued support for MongoDB versions 5.0 and 6.0 as they have reached their official end-of-life (EOL). Workspaces running either version are required to upgrade to MongoDB 8.2 before moving to Rocket.Chat v8.0.0. It is important to back up your data before this upgrade to prevent unintentional data loss or potential service disruptions. ⚠️

• Removed the Streamhub service and  deprecated DISABLE_DB_WATCHERS environment variable.

• Removed SMS integration settings for Mobex and VoxTelesys, leaving Twilio as the only supported integration for configuring SMS gateways in your workspace.

• Removed Enable second layer encryption for data transport setting.    

• Eliminated the built-in Logs tab, Log View Limit setting, and stdout streaming features. Rocket.Chat no longer provides in-app log viewing as workspace logging is now handled exclusively at the infrastructure level. Visit Monitor Workspace Logs and Metrics for more details.

• Removed Tokenpass OAuth integration from the workspace. Workspaces using Tokenpass must migrate to a supported OAuth or SAML provider to prevent authentication failures and user lockouts.

• Removed the outdated Game Center and WebRTC-based Livechat call features.

• Undeprecated the /v1/users.createToken endpoint that was previously scheduled for removal and enforced additional security requirements. Administrators must configure the CREATE_TOKENS_FOR_USERS_SECRET environment variable and include this shared secret in all requests to restrict token generation to authorized users.

• Removed the deprecated Off-the-Record (OTR) messaging feature, WebRTC admin settings, and Omnichannel Voice channel (VoIP) feature.

• Removed the Omnichannel Current Chats feature in favor of the Contact Center, which now serves as your unified interface for managing all chats, contacts, and calls in one place.

• Undeprecated the /v1/e2e.updateGroupKey endpoint.

• Removed the deprecated VoIP architecture that relied on the old FreeSwitch integration, including related permissions, Team Voice Calls Enabled setting, and FreeSwitch Integration section.

This release introduces significant changes to the platform, including the removal of deprecated methods and endpoint. For more details on breaking changes, refer to the Deprecated and phasing out features document.

What’s new

• Introduced Attribute-Based Access Control (ABAC) for private channels and private teams, allowing workspace administrators to define access rules based on user attributes rather than static role assignments alone. This enables more granular control over who can discover and join private spaces, helping organizations enforce security, compliance, and organizational boundaries at scale.

• Native Federation (Beta) adds built-in support for the Matrix protocol, enabling secure communication between independent Rocket.Chat and Matrix-compatible servers without external homeservers. Users can create federated direct messages and channels, manage invitations with clear status visibility, and apply roles and permissions consistently across federated rooms. Federation is configured natively in Rocket.Chat, simplifying setup and improving visibility into federated activity through system messages and contextual panels. Native Federation is in beta and recommended for evaluation and non-critical use cases only.

• Added Voice calls improvements, including a call history page to track all internal and external calls, featuring call outcomes, durations, and quick-action buttons to redial or jump straight to a chat. With this release, the Voice feature has exited the Beta phase and is now generally available. VoIP error logging and diagnostics have also been significantly improved to make troubleshooting easier and more actionable.

• Added the features in preview to the stable state, now quick reactions, timestamp parsing in messages, resizable contextual bar, and the enhanced navigation experience are available by default.

• Inverted the position of the buttons in the “Unique ID change detected” modal, highlighting the configuration update option instead of the new workspace option to avoid accidentally creating a new workspace registration.

Bug fixes

• Fixed an issue with the Global Search “Jump to message“ feature, resolving navigation issues.

• Fixed an issue where the client failed to load properly when the “First Channel After Login” setting began with a hash symbol (#), ensuring users are routed to the correct channel.

• Addressed an issue with Omnichannel tags being displayed even when “Request tags before closing conversations” setting was disabled. Now tags can be removed when the setting is enabled and later disabled.

• Fixed an issue related to unconfigured Drachtio transports and corrected WebRTC instructions for incoming external calls.

• Fixed an issue that caused Third-party login to not work properly. Now the third-party authentication works reliably with improved token handling.

• Resolved an issue where Omnichannel agent assignments in microservice deployments did not follow the chat limit. Now the maximum concurrent chat limit is followed.

• Addressed an issue where the /v1/users.logout endpoint caused logged-out devices to be displayed on the “Manage Devices” page. Now all logged-out sessions are marked correctly.

• Fixed a 2FA issue where changing the password caused the modal to be displayed repeatedly.

• Resolved startup issues when embedding Rocket.Chat in web clients using iframe.

• Resolved role assignment precedence in SAML, now SAML-specific default roles take priority over global registration roles, and prevent role merging when both are configured.

• Fixed an issue where the SAML “Default User Role” setting would fail when a role name was used instead of an ID. The setting now accepts both role name and role ID.

• Addressed an issue in rooms where the multi-select input did not allow removing selected users from the field.

• Patched an issue where the user's custom status was not saved correctly.

• The title and value parameters are now mandatory in the attachment.fields property when sending message attachments using chat.postMessage and chat.sendMessage endpoints , as well as incoming webhook integrations.

• Fixed an issue where message content could be exposed in logs when log level 2 was enabled. User and channel message data were being written to stdout during outgoing webhook checks, even when no outgoing webhooks were configured. Message body content has been removed from debug logs to prevent unintended exposure.

For more detailed information, check out our GitHub release page.