v3.8.1 January 25, 2026

Version 3.8.1, a minor release, includes:

• New features

• Enhancements

New features

This section describes the new features added in version 3.8.1.

1 - Coro console

The following features have been added to the Coro console:

1.1 - Notifications to root MSP admin users when a child workspace is created

Root MSP admin users are now notified by email when a child workspace is created in their hierarchy.

1.2 - Configure allowed bundles and modules at the subchannel level

MSP admin users can now customize the allowed bundles and modules for subchannel workspaces. By default, subchannels inherit these settings from their parent workspace, but MSP admin users can now limit access to a subset of those options. Any descendant workspaces inherit the selected bundles and modules from the subchannel.

For more information, see Editing subscription rules for subchannel workspaces.

1.3 - Security gaps

The following security gaps have been added and are available in both workspace and global views:

• Cloud Security
  • Cloud Application Connected (Additional Setup Required)
  • Access Permissions Added, No Auto‑Remediation Selected
• Devices
  • Coro Agent Reboot Required
  • Coro Agent Protection Limited by Outdated Version
• Endpoint Data Governance
  • Initial Privacy Sensitive Data Configuration Incomplete
• User Data Governance
  • Initial Privacy Sensitive Data Configuration Incomplete

For more information, see Managing Security Gaps.

1.4 - German language support

The Coro console now includes support for German.

2 - Cloud Security

The following feature has been added to the Cloud Security module:

2.1 - Cloud application policies connectivity status

Coro now clearly flags when detection is disabled for cloud applications due to missing required permissions or audit log access. Access permission policies only go into effect after the applications are fully protected:

• All required permissions are granted.
• Audit log is enabled and syncing.

For more information, see Configuring cloud security policies or Third-party applications.

3 - Network

The following features have been added to the Network and SWG sections of the console:

3.1 - Edit region from Network Settings

Admin users can now update the Network service region from the Network Settings page.

For more information, see Editing the Network service region.

3.2 - Network status on Devices page

A new Coro Network Status appears on the Devices page when the workspace has Coro Network enabled and the device is in a label associated with ZTNA or VPN. Status options include:

• Currently active
• Active last 24 hours
• Active last 7 days
• Active last 30 days
• Not recently active
• Never active

For more information, see Device information and options.

4 - Connectors

The following feature has been added to the Connectors section of the console:

4.1 - ConnectWise PSA ticket integration

Coro now supports ticket synchronization with ConnectWise PSA on mapped ConnectWise service boards. Tickets include structured details and direct links to the corresponding tickets in the Coro console.

For more information, see Integrating with ConnectWise PSA.

5 - Coro AI

The following feature has been added to Coro AI:

5.1 - AI auto-remediation

The Coro AI assistant can now execute approved remediation actions from the ticket summary. Admin users can authorize the AI assistant to apply all recommended actions, apply actions across multiple tickets, or apply individual actions as needed.

For more information, see Ticket summary.

Enhancements

Version 3.8.1 introduces the following additional changes:

1 - Coro console enhancements

1.1 - Windows Agent remote uninstall validation

Coro now validates device eligibility when remotely uninstalling the Windows Agent and displays confirmation dialogs, ensuring uninstall actions are applied only to supported Windows devices running Coro Agent version 3.7 or later.

For more information, see Uninstalling Windows devices from the Coro console.

2 - Data Governance

2.1 - Ticket findings section improvements

For User Data Governance and Endpoint Data Governance tickets involving sensitive data detection, the Findings section is now sub-grouped by detection source. For example, where Coro detects exposure of Personal Data in emails, findings for that type are displayed sub-grouped by the location of the detection. For example, in the email body, the subject, or a named file.

For more information, see User Data Governance: Reviewing policy violations and findings and Endpoint Data Governance: Reviewing sensitive data findings.

3 - Email Security

3.1 - Improved end-user blocked emails report

To reduce the incorrect classification of the Coro end-user blocked emails report as phishing or spam, Coro now sends an email with a significantly improved design providing more context and details about the report contents.