Account linking
Optional. Lets a user connect the identity they use inside your embed to a personal Designa account, so their design library is available in both places.
Not yet available
The API behind account linking exists, but there is no UI entry point for it inside the embed yet — the flow described below isn't something your users can trigger today. Don't build against this page until Designa confirms it's live.The flow
- Inside the embed, the user clicks the link icon on the credits pill.
- This mints a short-lived, single-use token tied to their embed identity.
- A tab opens to
app.designa.ai, top-level (not inside your iframe), where the user signs into their own real Designa account. - They see a consent screen confirming the link, and confirm.
Proof of identity is controlling both sessions at once — the embed session and the real-account session — not any email address the partner asserts, since a partner-asserted email is unverified and could otherwise be used to hijack an unrelated real account.
What linking does — and doesn't do
Design library
Once linked, the user's design library is unioned across both contexts and readable from either side. Editing an existing design from the "other" context falls back to save-as-a-new-copy — updates still require the original context.Credits are never shared
Linking does not merge credit pools. Work done inside your embed always bills your business's shared pool; work the user does directly onapp.designa.ai always bills their personal credits.Do you need this?
Skip it if your users only ever interact with Designa through your product. It's worth building if you expect the same person to also use app.designa.ai directly and want a single design library instead of two disconnected ones.