Projects overview

A project provides a unified editing interface in Studio for organizing related design‑time assets. In the global space each asset is independent; workflows, forms, and templates are listed without regard to relationships. Projects group assets that are part of the same initiative, for example, a workflow and its associated form and command templates. Grouping makes design, search, and management more straightforward.

Why use projects?

Projects help you organize related Studio assets and manage access.

Centralized organization: Keep all assets for an initiative in one workspace. The project sidebar and search cover every asset type.
Seamless environment promotion: Bundle Studio assets so you can move the project from development to test to production. Projects do not include non‑Studio items such as infrastructure bundles.
Shared editing: Multiple users see the same asset listing in a project workspace.
Asset reuse: Clone a project to reuse its assets for another use case.

Capabilities

Comprehensive asset management: Store workflows, forms, templates, scripts, and resource definitions in a single structured workspace.
Flexible project operations: Create new projects, import existing ones, clone projects, and use Project Builder to add assets during setup.
Team collaboration: Add collaborators, manage roles, and view all project assets in one shared list.
Portability: Export or import entire projects so all contained assets move together between environments.
Logical separation: Keep automations for different use cases (device upgrades, compliance tasks, provisioning) in separate projects.

When to use projects

Projects are especially useful when you want a cleaner design‑time experience than the global space provides. For example:

You’re building a multi‑component automation with several workflows, forms, or templates and want a single sidebar and search across all of them.
Multiple contributors must work on the same set of assets without wading through unrelated items.
You plan to promote assets through dev, test, and production as a coherent group of Studio files.
You want to standardize and reuse assets across similar automation initiatives.
You need consistent implementation for complex deployments such as switchport provisioning.

Terminology

Project: A workspace that holds related automation assets.
Assets: Workflows, JSON forms, command or analytic templates, transformations, etc.
Export/Import: Package a project for transfer between environments or teams.
Clone: Copy an existing project so you can modify or reuse it.
Project Builder: A guided interface for creating a new project with the right structure.
Operations Manager: The application that runs project workflows; job names include the project name.

How projects relate to other assets

Projects integrate with Itential tools. Studio hosts the projects workspace and management UI. JSON Form Builder generates forms that you can save as project assets. Operations Manager runs project workflows and tracks their progress.

Misconceptions

Projects organize only Studio assets. They are not a universal bundler for Platform.
A project works best when it groups closely related assets.
Moving an asset from the global space to a project does not automatically fix references inside the asset; you may need to update links manually.