Projects provide a centralized workspace in Studio where you can organize assets like Workflows, Command Templates, Transformations, and JSON Forms in a single location. Projects are containers that group components like workflows, forms, templates, and integrations for specific automation initiatives—whether you're managing device onboarding, software upgrades, or configuration compliance.
Why use Projects?
Projects transform how you build, manage, and scale automation by bringing structure and collaboration to your automation efforts.
Centralized organization
Keep all automation components for a specific initiative in one place. Projects eliminate the need to search across multiple locations by providing a dedicated workspace for related workflows, templates, forms, and scripts.
Seamless environment promotion
Move projects from development to testing to production with confidence. Each project bundles all automation components and dependencies together, ensuring your entire automation solution transfers intact between environments as a single unit.
Enhanced collaboration
Enable multiple teams to work together effectively on automation projects. Projects provide shared workspaces where network operations, security teams, and other departments can collaborate while maintaining clear visibility into project assets.
Scalable automation
Build once, reuse everywhere. Clone existing projects and adapt them for new use cases, making it simple to scale successful automation patterns across your organization without starting from scratch.
Key capabilities
Comprehensive asset management: Store and organize workflows, forms, templates, scripts, and resource definitions in structured workspaces.
Flexible project operations: Create new projects, import existing ones, organize assets efficiently, clone successful projects, and use Project Builder for guided setup.
Team collaboration: Add collaborators, manage shared access, and maintain project visibility across departments and teams.
Complete portability: Export and import entire projects, ensuring all components and dependencies move together between environments.
Logical separation: Keep different automation initiatives organized by use case, such as device upgrades, compliance management, or provisioning workflows.
When to use Projects
Projects deliver the most value in these scenarios:
Multi-component automations: When your automation involves multiple workflows, forms, and templates that work together to complete a process.
Team-based development: When multiple team members need to collaborate on automation development and maintenance.
Environment management: When you need to promote automations through development, testing, and production environments reliably.
Automation standardization: When you want to create reusable automation assets that teams can leverage for multiple use cases.
Complex deployment scenarios: For processes like switchport provisioning that require consistency and repeatability across multiple implementations.
Starting in 2023.2, Itential encourages developers to utilize Projects to help standardize collaboration across teams when building workflows and addressing orchestration of use cases.
Understanding Projects terminology
Project: A workspace container that holds related automation assets and provides organizational structure.
Assets: Automation components including workflows, JSON forms, command templates, analytic templates, and transformations.
Export/Import: Packaging and transferring complete projects between environments or teams.
Clone: Creating copies of existing projects for modification and reuse.
Project Builder: Guided interface for setting up new projects with appropriate structure.
Operations Manager: Runtime environment where project workflows execute. The project name is included in the workflow name for clarity.
Integration with Itential products
Projects work seamlessly with your existing Itential tools:
- Automation Studio houses the Projects workspace and provides project management interfaces
- JSON Form Builder creates dynamic input forms that Projects include as reusable assets
- Operations Manager executes project-based automations and tracks completion
Projects serve as an organizational layer between development tools and runtime environments, enabling consistent deployment practices while supporting collaboration and governance across your automation lifecycle.