Skip to content

The workspace lifecycle

A Coro workspace can be in one of the following states during its lifecycle:

Note

When a workspace is not in Trial or Subscription state, for example, when a trial or subscription expires, the Coro platform no longer functions.

New

When a workspace is created, the New state is assigned. A workspace cannot return to the New state after transitioning to a different state. New workspaces have access to the initial modules listed below:

  • Cloud Security

  • Endpoint Security

  • Email Security

  • Endpoint Detection and Response (EDR)

Note

A workspace in a New state is not automatically transitioned to Trial state. An onboarding event trigger must first occur to transition a New workspace to Trial state.

Inactive

A workspace is classified as Inactive when it is in either Trial or Subscription state, and the trial/subscription expires. When a Trial ends and there is no active Subscription, the workspace reverts to an Inactive state.

Note

When an initial device is activated within a trial workspace prior to the trial's expiration date, the workspace reverts to a Trial state for an additional 30 days.

If additional devices are activated within a trial workspace prior to the trial's expiration date, the workspace reverts to an Inactive state after 30 days.

When a workspace is in an Inactive state:

  • 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

A workspace moves into a Trial state when it is currently in a New state and an onboarding event trigger occurs for the first time, for example, a cloud app is connected, a device is activated, or an inbound gateway is set up.

Note

Logging into the Coro Platform is not considered an onboarding trigger, and therefore does not transition a workspace from New to Trial state.

Once activated, a workspace remains in a Trial state for a period of 30 days if no endpoint devices are activated.

Note

When an endpoint device is activated within the workspace, the workspace Trial state is extended for an additional 30 days.

Remember

A workspace in a Trial state cannot be manually extended.

When a workspace is in a Trial state:

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

  • All tickets (for protected and unprotected users) are displayed in the Actionboard panels

    Actionboard panels

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

Subscription

A workspace is classified as Subscription when an MSP administrator selects Start Subscription from the actions menu of the workspace within the MSP Portal:

Note

The Start Subscription action is available to workspaces in Inactive, Trial, or New state.

Activate a bundle

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

Inactive child workspaces can be archived. When a workspace is archived, any cloud applications are disconnected and Network settings are cleared. Admin users can’t sign into archived workspaces. For more information, see Archive a workspace.

The archived workspace can be restored as an inactive workspace. For more information, see Restore a workspace.