Projects and Organizations¶
Organizations and projects help separate operating boundaries, credentials, pipelines, workspaces, storage, and administrative access.
Organization¶
An organization represents a security and operating boundary within SchemAlign.
Organizations can model a full tenant or customer, but they can also represent functional areas, distributed IT teams, departments, or shared/global resources.
Examples:
This allows teams to manage their own integrations without accidentally exposing one area's workspaces, accounts, storage, pipelines, runtime data, or operational outputs to another area. For example, Advancement may manage donor-system integrations while Admissions manages application or CRM-to-ERP integrations, with each area isolated unless shared/global access is intentionally configured.
Project¶
A project groups related integration work inside an organization.
Examples:
Access model¶
A user's access may vary by organization. SchemAlign uses organization-scoped roles so access can match each team's responsibilities without granting unnecessary access across other operating boundaries.
| Organization role | Typical access |
|---|---|
Org Viewer (org_viewer) |
Can see the organization's visible pipelines, run history, logs, and operational status. |
Org Operator (org_operator) |
Can execute pipelines for the organization and review logs, run history, and outputs. |
Org Editor (org_editor) |
Can create and edit projects for the organization. |
Org Admin (org_admin) |
Can manage RBAC inside the organization, including user memberships and role assignments. |
Roles are scoped to the organization
A user may be an admin in one organization, an operator in another, and have no access to a third. This keeps functional areas separated unless shared or global access is intentionally configured.