Core Concepts¶
SchemAlign is organized around a small set of product concepts. Understanding these concepts makes the rest of the documentation easier to follow.
Root navigation model¶
The main SchemAlign application is organized around six root areas:
| Area | Primary purpose |
|---|---|
| Overview / Command Center | Monitor system health, build dates, integration health, run history, and environment totals |
| Triggers | Automate pipeline launches through schedules, HTTP triggers, and future event patterns |
| Workspace | Build, test, run, and review integrations |
| Storage | Inspect physical files, artifacts, and logs |
| Accounts | Manage service accounts and connection profiles |
| Admin and Extend | Manage RBAC, organizations, users, and controlled custom node development |
Product concepts¶
Projects and organizations¶
Organizations separate security and operating boundaries. Projects group related integration work inside those boundaries.
Pipelines and nodes¶
Pipelines are integration workflows. Nodes are the reusable steps that read, prepare, route, write, store, or send data.
Artifacts¶
Artifacts are physical or runtime outputs produced by pipeline runs, such as files, responses, logs, or transformed datasets.
Runtime values¶
Runtime values let supported fields resolve named values, such as {{current_term}} or {{sysdate}}, when a node executes.
Start with Workspace
If you are learning SchemAlign as a builder, start with Workspace. It is where the product model becomes visible through actual integration design.