Organizing content: what changed from OpCon Classic
This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.
What this solves
In OpCon Classic you separated content with Departments. In OpCon Continuum you use Workspaces: a container that groups and isolates a team's or application's content (workflows, scripts, properties, thresholds, resources, and service requests). Same goal, a cleaner container, so mapping your Departments to Workspaces is the first organizing step.
What you get. How Classic Departments map to OpCon Continuum Workspaces, and how to set one up so a team's content stays its own.
Related topics
- Manage workspaces (Administrator)
- Manage roles and permissions (Administrator)