BetaThis documentation is in beta. Content continues to evolve with Continuum development prior to General Availability.
Automation export and import
Moving a bundle of workflows, calendars, frequencies, properties, thresholds, resources and tags between environments or tenants — what the bundle contains, what export deliberately leaves out, and the overwrite and all-or-nothing rules import applies.
Custom fields
How to add your own tenant-global metadata fields to jobs, what each definition field controls, where values are set, and which input types are available.
Environments
What an environment is as a deployment target for workflows and service requests, the fields and service health it reports, and why a newly created one may still be provisioning.
Light and dark appearance
The Light, Dark and System colour scheme choice in the Account menu — what each one does, where the choice is stored, and why it is per browser rather than per account.
Manage custom fields
How to create, edit and delete custom fields so you can capture and track additional information on jobs across your environment.
Manage environments
How to create and manage environments so you can separate and promote work across development, test, and production.
Manage permissions
How to use the Permissions page: roles, permissions and scopes that control who can see and change what, event identities for scripts and machines, and workspaces that keep teams' content apart.
Object naming
The character policy and length bounds that apply to the names you give properties, tags, calendars, frequencies, scripts, service requests, and every other named object, the objects that keep their own stricter rule, and what happens when you edit an object whose name predates the policy.
Organizing content: what changed from OpCon Classic
How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.
Roles and permissions
How roles, the permission catalog, and per-scope grants in workspaces and environments shape what each person sees in Continuum, where the Permissions page lives, and the refusals that apply to every event.
Workspaces
How workspaces group and isolate workflows, properties, thresholds, resources, scripts, and service requests, where they are managed, what stays global, and why access comes from role grants rather than workspace membership.