Deprecated and phasing out features

This document outlines features that are no longer supported in Rocket.Chat or are scheduled for removal in future updates (deprecated). It also serves as an early notice for workspace managers to adjust and optimize their workspaces accordingly. Please note that this information is subject to change with future releases and may not include every deprecated feature.

Breaking changes in upcoming versions

Rocket.Chat v9.0.0

Removal of deprecated features

• API parameter replacements and removals: The following deprecated API parameters will be removed in v9.0.0 to mitigate security risks and improve performance.

Rocket.Chat v8.0.0

Architectural and database updates

• We have officially discontinued support for MongoDB versions 5.0 and 6.0 to mitigate security risks 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.

• The Streamhub service and the deprecated DISABLE_DB_WATCHERS environment variable have been removed as part of ongoing efforts to simplify the platform architecture and deployment model. Streamhub is no longer required for real-time communication in current workspace setups. You can safely remove the streamhub microservice and  DISABLE_DB_WATCHERS from your configuration.

Omnichannel and marketplace enhancements

• We have pruned unused SMS integrations, specifically eliminating the settings for Mobex and VoxTelesys. Twilio will remain the only supported integration available for configuring SMS gateways in your workspace.

• WebRTC-based Livechat calls and all associated features, including the Meet page, are outdated and have been removed. Workspaces that require synchronous communication in Omnichannel can integrate video conferencing solutions through Apps-Engine or the Rocket.Chat APIs.

• The outdated Game Center feature has been removed to reduce clutter, as games are no longer available on the marketplace.

Security and administration changes

• Tokenpass OAuth settings are no longer available on the workspace. If your workspace still relies on Tokenpass for user authentication, update your configurations to use a supported alternative OAuth or SAML provider to avoid potential authentication issues and locking users out.

• Enable second layer encryption for data transport setting is discontinued and will no longer be available.

• The Logs tab in Reports has been removed, leaving only Analytics. Log View Limit settings and all log streaming features (including stdout streaming, related APIs, permissions, and runtime log queues) are cleared from the codebase. This change addresses the security and reliability limitations of the built-in log view, especially in multi-instance and microservices production setups. Workspace admins are advised to use the recommended monitoring stack available in the official deployment configuration, which provides Prometheus-based data collection and Grafana dashboards for observing workspace activity.

Rocket.Chat Voice improvements

With the launch of the new Rocket.Chat Voice architecture, the deprecated VoIP architecture that relied on the old FreeSwitch integration is being completely cleared from the codebase. This change does not eliminate FreeSwitch compatibility. Instead, the deprecated FreeSwitch Integration is being replaced with a generic SIP integration that remains fully compatible with FreeSwitch and other SIP-compliant infrastructures.

Due to this removal, workspaces relying on the legacy integration must prepare for the following:

• FreeSwitch components removed: The old VoIP integration with FreeSwitch is removed. This includes all associated technical components, such as extension management APIs and the collection of VoIP statistics related to FreeSwitch connections and extensions.

• New settings for routing calls: Legacy settings such as the FreeSwitch Integration section and Team Voice Calls Enabled setting are removed from the workspace UI. Rocket.Chat Voice is now automatically enabled when the Voice add-on is active, allowing intra-workspace calls via standard WebRTC without additional configuration. A dedicated SIP Integration setting is now available for routing calls through external SIP infrastructure.

• VoIP permission changes: The legacy permissions  Manage Voice Calls, View Voice Call Extensions, and Allow Voice Call are removed. Granular permissions have been introduced to grant access to internal and external calling features in the new Rocket.Chat Voice architecture.

Removal of deprecated features

Several deprecated features will be removed in v8.0.0 to simplify the codebase, improve performance, and mitigate security risks.

• OTR feature removed: We have removed the Off-the-Record (OTR) messaging feature designed for exchanging temporary client-side encrypted messages, due to low adoption. For encrypted messaging, consider using End-to-End Encryption (E2EE). E2EE provides improved encryption capabilities that align better with the platform’s core security features.

• Omnichannel Voice Channel (VoIP) removed: The Omnichannel Voice channel feature is removed, along with its associated API endpoints and permissions. Its Asterisk-based implementation does not support highly scalable, cloud-native VoIP workloads. For voice requirements in Omnichannel, consider integrating scalable VoIP providers or call-center platforms using supported APIs or extensions. Rocket.Chat can also be embedded into third-party call-center solutions using Chat Engine, enabling chat-based communication with your existing VoIP infrastructure.

• WebRTC admin settings removed: The WebRTC workspace administration settings are no longer in use and are removed completely.

• API endpoint replacements and removals: The following deprecated API methods and endpoints are removed, with some being replaced by improved alternatives:

• API parameter removals: The following parameters have been permanently removed from their respective API endpoints in v8.0.0:

These changes are vital for ensuring the long-term stability and security of the Rocket.Chat workspaces. Workspace administrators should begin evaluating their current configurations now to facilitate a seamless upgrade to version 8.0.0. For detailed information, check out our GitHub release page.

Rocket.Chat v7.0.0

Platform and database enhancements

• We have upgraded the platform to Meteor 3.0 and Node.js 20, bringing in the latest security improvements, bug fixes, and performance optimizations. However, this update may require environmental adjustments, especially if your application relies on older Node.js features or Meteor packages. Developers should review their environment and ensure all dependencies are compatible with these new versions.

• With MongoDB 4.4 reaching end-of-life, we have discontinued its support in favor of MongoDB 7.0. The new version offers enhanced performance, security improvements, and new features like support for multi-document ACID transactions. MongoDB 5.0 is now deprecated. If you're still using MongoDB 4.4 or 5.0, an upgrade is necessary to maintain compatibility with our platform. It’s important to test your database migration thoroughly to avoid potential data or performance issues.

Security and compliance updates

• Removal of Compatible Sandbox (vm2) for Integration Scripts: We've fully removed the Compatible Sandbox option for integration scripts. Previously, Rocket.Chat allowed users to choose between two sandboxing libraries for script execution: vm2 (Compatible Sandbox) and isolated-vm (Secure Sandbox). Due to critical security vulnerabilities and lack of ongoing support for vm2, it is no longer available as of version 7.0. All scripts will now run exclusively in the Secure Sandbox environment. This change may impact integration scripts that relied on vm2's behavior. Review your integration scripts to ensure they are compatible with the secure sandbox.

• Enhanced security for app installations: Starting with this release, the ability to upload private apps is now restricted to our premium plans (Starter, Pro, and Enterprise). This change helps us maintain the integrity of Rocket.Chat's customization options while safeguarding the exclusive features of our paid plans. By limiting private app uploads, we ensure that only licensed users can fully tailor their experience, protecting the value and security of our platform.

• The ability to install apps from a URL will be removed.

• Unused settings such as UI_Click_Direct_Message and the view-history permission have been removed to comply with security best practices and reduce clutter.

Permissions and endpoint enhancements

• New permissions for room management in teams: New permissions (create-team-channel and create-team-group) have been added to enhance control over room creation within teams. These permissions integrate closely with team management functions and ensure proper visibility and control.

• Improved error messaging for login attempts: The login process will no longer suggest which credential is incorrect, returning a generic "Unauthorized" error instead to enhance security.

• Disabled query and fields API parameters: The query and fields parameters have been disabled and can only be enabled by setting the ALLOW_UNSAFE_QUERY_AND_FIELDS_API_PARAMS: true environment variable. Enabling them may expose your workspace to security breaches, for which Rocket.Chat is not responsible. These parameters will be completely removed on 9.0.0.

Omnichannel and integration adjustments

• Fixes for stuck omnichannel rooms: A migration will correct the statuses of inquiries linked to rooms that are closed but still listed as active due to systemic issues.

• Removed dependencies: The dependency on the meteor/check package has been removed from all v1 endpoints to avoid errors and enhance performance.

Air-gapped workspace restrictions for commercial licensing

Starting with this release, Rocket.Chat Community Edition will no longer support air-gapped environments (environments without internet access). To ensure compliance with licensing agreements, only users on premium plans—including the free Starter plan—can run Rocket.Chat in these air-gapped setups. Our standard builds include commercial code, so restricting air-gapped environments to premium users helps maintain security and proper licensing compliance. Community users who need Rocket.Chat without commercial restrictions can use the fossify script. This tool removes all premium code, leaving a fully open-source version with no limitations (e.g., no user or MAC limits). While this doesn’t include our commercial air-gapped setup, it allows users to build their own offline solutions and customize them on top of our open-source code as they wish. For details, check out the fossify script.

Removal of deprecated features

Several outdated features have been removed to streamline the codebase and improve overall system performance:

• HipChat importer removed: Due to the discontinuation of HipChat, the HipChat importer is no longer supported. If you’re still migrating from HipChat, consider using alternative import methods or manually migrating your data.

• Unused oauth settings removed: We’ve pruned unused and outdated OAuth settings to simplify the configuration process. The button text color and button color settings will be removed. If your system still relies on these deprecated settings, update your configurations to avoid potential authentication issues.

• API endpoint replacements and removals: The following older API methods and endpoints have been deprecated in favor of newer, more efficient ones.

• The following parameters have been removed and replaced.

This update is critical for maintaining the operational integrity, security, and efficiency of Rocket.Chat workspaces. Workspace managers should review these changes carefully and begin preparations for a smooth transition to version 7.0.0.

For detailed information, check out our GitHub release page.