Embed Prismatic

Embedding lets the user's customers manage integrations without leaving the user's app. The backend signs a short-lived JWT for the signed-in user; the browser passes it to the @prismatic-io/embedded SDK, which renders Prismatic screens in an iframe. Use the embedding docs and the installed SDK's public types for current behavior, and prism --llms and command --help to discover Prism's organization and signing-key commands.

Start from the user's request and the current application. Identify the frontend framework, the backend, the existing authentication and session model, how a user maps to a tenant, where configuration and secrets come from, and the existing tests. Extend the app's own patterns: its router, auth middleware, API client, config module, and test setup. Infer technical choices from the code. Ask only about business decisions the code cannot answer, such as which app tenant is a Prismatic customer, which screens to embed, where they go, and who may see them.