Overview

A workspace is the top-level logical container in the CDN architecture that organizes all resources for a single application or service. It isolates service hostnames, routing logic, edge rules, and variables within a single dedicated boundary, ensuring that changes you make within one workspace have zero impact on others.

Similar to a Git repository, each workspace holds one application with multiple environments. This provides clear ownership, aligns resources with the development life cycle, and lets teams safely test and promote configurations before they go live.

In practice, you use a workspace to:

• Control access through scoped permissions. Each workspace is assigned a primary group ID for the team that owns it, along with additional group IDs to grant specific view or audit access to outside teams.
• Manage global settings. You define global variables once at the workspace level, but teams can override specific values for individual environments when needed.
• Advance your application through life cycle stages. Teams can clone a production environment down to a lower environment, allowing them to develop, test, and promote changes with a clear version history and audit trail.

📘

Multiple environments are not supported during Delivery Manager Beta.

Workspace components

There are multiple components that you can configure at the workspace level:

• Environments. Isolated deployments that define your content delivery context.
• Service hostnames. Public-facing domains for your application or service.
• Routes. Used to map service hostname sets to environments.
• Variables. Value-based containers used to define and update parameters within rules and settings.