Skip to Content
This documentation is provided with the HEAT environment and is relevant for this HEAT instance only.
Core ConceptsProjects

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

Note: The following functionality is in development and not yet available in the current release.

Future releases of HEAT will introduce project-based access control. This enhancement will allow administrators to assign or revoke permissions at either the Project or Session level, granting more granular control over who can:

  • View and manage Sessions within a specific Project.
  • Modify or create Session Templates tied to that Project.
  • Access or generate analytics for Sessions they’re authorized to see.

With these ACL features in place, administrators will be able to configure roles that restrict visibility and actions across different Projects—particularly useful for organizations with multi-tenant or cross-department requirements.

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.
  • Future project-based ACLs will provide more nuanced permissions, improving security and collaboration across diverse teams or departments.

Next Steps

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