Project integrations

Bind the exact account and resource

A user may authorize several accounts, but each Iterel project selects its own connection and remote resource under Project settings → Integrations. There is no most-recent-account fallback and no cross-project credential bleed.

What engines see

At run time Iterel builds a short-lived, project-scoped integration gateway. Only namespaces granted to that project appear to the engine. Browser verification, Supabase, Vercel, GitHub, and other supported services share the same per-run attribution model.

Attach a source

The relevant composer + menu lists integrations configured for the current project. Choosing an integration attaches a source link or imported reference to pending work; it does not silently invoke a capability. Figma frame import is the exception in shape: it is an explicit Design + tool, shown only for the exact usable project binding, and creates/binds a Task before applying frames.

Setup discipline

Connecting an integration, enabling CLI credential injection, or repairing an expired authorization becomes a tracked setup task with verification steps. Raw credentials are never written into the workspace.