About Spaces and Workspaces

In Assets, spaces serve as the highest-level containers for assets and governance, while workspaces allow experimentation and parallel development inside a space. Understanding when to use each helps you keep assets organized, compliant, and adaptable.

A space is a central repository for all your digital assets, metadata, and configurations related to a specific brand, team, or initiative.

• Each space is independent, assets, roles, and settings in one space do not affect another.
• Spaces define governance boundaries: roles, permissions, and settings are scoped at the space level.
• Spaces can be linked to one or more CMS stacks, allowing assets to be reused seamlessly inside content entries.

• To manage assets for different brands (e.g., contentstack.com/product-marketing, contentstack.com/docs, or contentstack.com/academy).
• To create separate environments for legal or regional requirements.

Within a space, you can create workspaces. Workspaces act as parallel environments where assets and schemas can evolve independently. They are similar to branches in Git or Contentstack Headless CMS.

• Workspaces are typically used to test or experiment without affecting the main workspace.
• Each workspace has a parent-child relationship as new workspaces are forked from another workspace.

Note Every space includes a main workspace that serves as the primary workspace. Any new workspace you create becomes a fork of the main (or another parent workspace), inheriting its assets and configurations. In other words, when a workspace is forked, it inherits assets, metadata, and configurations from its parent. Changes made in the child workspace remain isolated and do not affect the parent. This forking model allows safe experimentation while keeping the main workspace stable.

• To prepare seasonal or campaign-specific assets without affecting the main workspace.
• To experiment with new asset schemas or metadata before rolling them out globally.
• To align with CMS branching workflows, ensure assets stay in sync with content changes.

• Use spaces for long-term organizational separation (eg., brands, regions).
• Use workspaces for short-term or experimental work (eg., campaigns, testing).
• Avoid over-fragmentation (too many small spaces/workspaces increase complexity).

By combining spaces and workspaces correctly, Assets provides both structural clarity and operational flexibility, ensuring assets are always organized, governed, and adaptable.