This page is intentionally minimal. If you need the full embedded implementation flow, use SDK integration. If you need authentication pattern selection or token lifecycle guidance, use Authentication. If you need Azure OIDC sign-in or request-level API auth handling, use Authentication guide. If you want installable client libraries first, use SDKs. If you need field-by-field settings, use Configuration reference.
Success criteria
1
Confirm the three prerequisites
You need a Connected App, a backend token route, and a frontend page where the SDK can mount.
2
Render one SDK container
Add a single mount target and load the SDK script.
3
Attach a fresh Embed Token
Fetch a short-lived token from your backend and set it on the container.
4
Validate capability loading
Confirm sign-in state, then verify Coach, Money, and Growth surfaces can each render expected user-facing data.
If the container renders and core capability checks pass, your baseline integration is ready.
Where to go next
SDKs
Install official JavaScript and Python SDKs before wiring custom HTTP clients.
Integration guide
Move from basic validation to the full tenant integration path and delivery checklist.
Tenant embedding guide
Decide how to load the SDK, when to fetch tokens, and whether to use declarative or imperative boot.
Configuration reference
Look up required fields, types, validation rules, and example configuration sets.
Authentication
Review authentication pattern selection, token lifecycle, and embedded auth boundaries.
Authentication guide
Use Azure OIDC sign-in, API auth, refresh, and sign-out guidance when your integration goes beyond the embedded quickstart.