Skip to content

The workspace lifecycle

Coro classifies workspaces into lifecycle statuses. The status of a workspace defines its operational capabilities and access within the Coro platform. Workspaces can be in one of the following statuses during their lifecycle:

MSP administrators and admin users with sufficient permissions can view their respective workspace statuses from the list of workspaces in the Manage Workspaces portal.

New

Coro assigns the "New" status to a workspace upon creation. After a workspace transitions to a different status, it cannot revert to the "New" status. New workspaces are granted access to the following modules:

  • Cloud Security

  • Endpoint Security

  • Email Security

  • Endpoint Detection and Response (EDR)

Note

A workspace with a "New" status does not automatically move to "Trial" status. There must be an onboarding event trigger for a new workspace to transition to trial.

Inactive

Coro classifies a workspace as inactive if it is in "Trial" or "Subscription" status and the trial or subscription expires. If a trial ends without an active subscription following it, Coro automatically changes the workspace's status to "Inactive".

Note

When an admin user with sufficient permissions activates an initial device within a trial workspace prior to the trial's expiration date, the workspace reverts to a "Trial" status for an additional 30 days.

If an admin user activates additional devices within a trial workspace prior to the trial's expiration date, the workspace reverts to an "Inactive" status after 30 days.

When a workspace is inactive:

  • No data is monitored, and no tickets are generated.

  • Module independent assets remain associated with the workspace, for example, users, cloud apps, and devices. This ensures efficient onboarding if the workspace subscription is renewed.

  • Module dependent assets, for example, infrastructure required to keep a particular module feature functioning are discarded.

Trial

Coro classifies a workspace as trial when it is currently in "New" status and an onboarding event trigger occurs for the first time, for example, a cloud application is connected, a device is activated, or an inbound gateway is set up.

Note

Signing into the Coro platform is not considered an onboarding trigger, and therefore does not transition a workspace from "New" to "Trial" status.

After activation, a workspace remains in "Trial" status for a period of 30 days if no endpoint devices are activated.

Note

Activating a device within the workspace extends its trial period by an additional 30 days.

Note

You cannot manually extend a workspace's trial period.

When a workspace is in a trial period:

  • Data is monitored, and tickets are generated for both protected and protectable users.

  • All tickets (for protected and protectable users) are displayed in the Actionboard.

    Actionboard panels

  • Tickets are generated for all devices in both Visibility mode and regular mode.

Subscription

Coro classifies a workspace as subscription when an MSP administrator selects Start Subscription from the actions menu of the workspace within the Manage Workspaces portal:

Activate a bundle

Note

The Start Subscription action is available to workspaces in inactive, trial, or new state.

When a workspace is in a subscription state:

  • Data is monitored, and tickets are generated for protected users.

  • Tickets are generated for all devices (Visibility mode and regular mode.)

Archived

MSP administrators and admin users with sufficient permissions can archive inactive channel, child, and regular workspaces. When a workspace is archived, any cloud applications are disconnected and network settings are cleared. You can’t sign into archived workspaces. For more information, see Archive a workspace.

You can restore an archived workspace as an inactive workspace. For more information, see Restore a workspace.