Skip to content

SSO / SAML

SAML SSO for signing into Proyecta itself is on the roadmap. For SSO inside the apps you build, ask the AI to integrate any provider.

There are two distinct “SSO” stories that often get conflated. This page covers both.

1. Logging into the Proyecta builder itself

Section titled “1. Logging into the Proyecta builder itself”

For signing into Proyecta — the builder, the dashboard, your account — Proyecta currently supports:

  • Email and password — traditional credential login
  • Google OAuth — sign in with a Google account
  • Microsoft OAuth — sign in with a Microsoft account

Email verification, password reset, and the standard account flows are wired up.

SAML / OIDC SSO for Proyecta platform login is planned but not yet available. When it ships, it will cover the standard enterprise providers — Okta, Microsoft Entra ID (Azure AD), Google Workspace, OneLogin, and any SAML 2.0 / OIDC IdP. If your organization needs Proyecta SSO today, contact sales — there may be an early-access path.

This is a different problem. If you want your end users to sign in via SSO when they use the app you’ve built in Proyecta, you have two options:

Option A: Use Proyecta Auth — built-in authentication with Google, Microsoft, and Email OTP out of the box. SAML/SSO via Proyecta Auth is available on the Business plan.

Option B: Bring your own provider — ask the AI to integrate a third-party auth provider directly. Common integrations:

  • Auth0"Add Auth0 to my app with SAML support so enterprise customers can SSO."
  • WorkOS"Integrate WorkOS so my customers can connect their own IdP for SSO."
  • Clerk"Set up Clerk authentication with SAML and SCIM."
  • Supabase Auth"Add Supabase Auth with email/password and Google sign-in."
  • NextAuth (Auth.js)"Wire up Auth.js with Google and a SAML provider."

Add your provider’s credentials to Environment Variables and the AI will write the integration.

  • SAML 2.0 SSO — bring your own IdP
  • OIDC SSO — modern alternative to SAML for newer IdPs
  • SCIM provisioning — auto-create and deprovision Proyecta accounts when employees join or leave
  • Domain capture — automatically route users from your verified domain into your org’s SSO
  • Per-org enforcement — require SSO for everyone in your organization