General environment and access administration.
View all tagsMoving 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.
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.
How to define custom fields so you can capture and track additional information on jobs across your environment.
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.
How to create and manage environments so you can separate and promote work across development, test, and production.
How roles, permissions, and scopes control who can see and change what, and how to assign them.
How to create and manage workspaces so you can organize work and control access by team or function.
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.
How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.
How roles, the permission catalog, and workspace and environment scopes shape what each person sees in Continuum, and the refusals that apply to every event.
How workspaces group and isolate workflows, properties, thresholds, resources, scripts, and service requests, what stays global, and why access comes from role scopes rather than workspace membership.