Projects

A Project is the primary organizational unit in SolutionEngine.

Every resource in the platform belongs to a project. Projects provide structural isolation, ensuring that workflows, datasources, environments, storage, and configuration remain separated from other systems.

Projects allow multiple independent systems to coexist within the same SolutionEngine instance without overlapping resources or configuration.

---

Purpose of a Project

Projects serve three main purposes:

1. Isolation
   Resources inside one project are not accessible from another. This includes datasources, workflows, models, storage, environment assignments, variables, and execution logs.

2. Organization
   Projects group related components together. A single project typically represents a specific system, deployment, or operational domain.

3. Access Control
   Team permissions and roles are assigned at the project level. This ensures that users only access the systems they are authorized to manage.

---

What a Project Contains

Within a project, you can define and manage:

• Datasources — Entry points that receive incoming data.
• Workflows — Node-based processing logic.
• Models — Registered models available for execution.
• Buckets — Storage for artifacts, structured outputs, and logs.
• Environments — Runtime targets assigned to execute workflows.
• Environment Variables — Project-scoped configuration values accessible within workflows.

All execution and storage activity is scoped to the project boundary.

---

Execution Scope

When a workflow is deployed to an environment, it remains associated with its project.

An environment can be assigned to a specific project, and it will only execute workflows belonging to that project. This prevents cross-project execution and ensures operational separation.

Logs and stored outputs generated during execution are also scoped to the originating project.

---

Creating a Project

To create a project:

1. Navigate to the Projects page.
2. Select Create Project.
3. Provide a name and optional description.
4. Confirm creation.

A unique identifier is generated automatically. This identifier is used internally to namespace project resources.

After creation, you can begin defining datasources, workflows, and environments within the project.

---

Project Configuration

Each project includes configuration sections for:

• General Settings — Project name and metadata.
• Variables — Key-value pairs accessible during workflow execution.
• Team Access — Role-based user permissions.
• Archive or Delete — Administrative lifecycle actions.

Archiving or deleting a project removes access to all associated resources.

---