Projects

Projects in HEAT serve as logical containers for Sessions and Session Templates. By grouping related workflows under a single Project, you can better organize data and processes, especially when dealing with multiple simulation engines or diverse integration targets.

Association Rules

• Every Session Template and Session in HEAT must be associated with exactly one Project.
• A default Project is provided out of the box, which may be sufficient for simpler deployments.
• You can create additional Projects to accommodate different training scenarios, simulations, or integration requirements within the same HEAT instance.

When to Use Multiple Projects

• Distinct Data Sources
  If you have multiple simulation engines or external data pipelines, creating separate Projects helps keep data, Session Templates, and Sessions organized and isolated.

• Different Requirements
  Projects can represent specific organizational units, security classifications, or engagements, each with unique data-handling or reporting needs.

• Testing New Workflows
  By creating a dedicated Project for development or proof-of-concept work, you can iterate on new Session Templates and data workflows without disrupting active simulations or well-known configurations.

• Simplified Management
  Splitting data into multiple Projects prevents monolithic setups, making monitoring and debugging more straightforward.

Project-based access control

Summary

• Projects are a fundamental building block in HEAT, grouping all Sessions and Session Templates.
• A default Project may suffice for smaller or single-simulator scenarios, but creating additional Projects can help organize and manage more complex, varied workflows.
• Project-based access control is not available today.

Next Steps

• Learn how workflows relate to Projects in Session Templates.
• Explore how data enters HEAT in Ingests.
• Check back for updates on project-based ACLs as HEAT’s authorization model evolves.

HEAT documentation team. Last updated 2 October 2026.