Authentication approach

The Infrenta application authenticates users through managed authentication (Supabase Auth), including enterprise sign-in options described on the Security page. The public marketing site and the authenticated application are separate hosts.

For people

Users sign in to the application host. Session, company membership, and role determine which projects and workflows they can access. See Accounts and access.

For systems

System-to-system access is not generally available as a public OAuth app or a self-serve token portal. When an integration is approved, credentials and scopes are issued as part of that implementation.

Do not embed user passwords in scripts. Do not share a personal session as an integration credential.

Company boundary

Every integration must honor company isolation. Credentials that can read Company A’s projects must not be usable against Company B.

If you need authentication details for a planned integration, discuss an integration. This page will be expanded when a public authentication contract exists.