Cloud SAML SSO (Per-App)

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Cloud SAML SSO (Per-App) working in a real project rather than a sandbox.

   Set up Cloud SAML SSO (Per-App) in this project — let end users of your Cloud app sign in through their IdP. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   B2B apps requiring customer SSO

   The record lists this as one of the jobs Cloud SAML SSO (Per-App) is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Cloud SAML SSO (Per-App) for B2B apps requiring customer SSO. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Cloud SAML SSO (Per-App) is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Cloud SAML SSO (Per-App) before I publish. Check any SAML 2.0 IdP via metadata URL and JIT user provisioning on first login, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Enterprise procurement requirements

   A second job the record lists for Cloud SAML SSO (Per-App), useful once the first path works.

   Extend this project so Cloud SAML SSO (Per-App) also covers enterprise procurement requirements. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Cloud SAML SSO (Per-App)?

  Cloud SAML SSO (Per-App) is Lovable's Cloud feature: Let end users of your Cloud app sign in through their IdP. Per-project SAML 2.0 SSO for end users of Cloud apps.

• Is Cloud SAML SSO (Per-App) GA or in beta?

  Cloud SAML SSO (Per-App) is generally available (GA) on Lovable.

• What Lovable plan includes Cloud SAML SSO (Per-App)?

  Cloud SAML SSO (Per-App) is available on Lovable's Lovable Cloud only plan.

• When did Cloud SAML SSO (Per-App) launch?

  Cloud SAML SSO (Per-App) launched on Apr 24, 2026.

• Lovable PaymentsSame category, also GA · Apr 2026
• App Emails (Transactional)Same category, also GA · Apr 2026
• Custom App EmailsSame category, also GA · Apr 2026