This page covers how a person signs in to ingestia.io and how the workspace owner hardens access to accounts. For automatic provisioning through a corporate IdP (SAML/OIDC + SCIM), see SSO and SCIM.
What it is#
Authentication decides who you are (identity). It's different from what you can do (roles/RBAC) and from which rows you see (RLS). One person can belong to several workspaces with the same sign-in identity.
Available sign-in methods#
| Method | How it works | Status |
|---|---|---|
| Social sign-in (Google Sign-In). Optional restriction by Google Workspace domain. | Available | |
| Email + password | Self-service sign-up; password stored as a hash (scrypt), never in plain text. Set at sign-up — there's no self-service change or reset. | Available |
| MFA (TOTP) | Second factor through an authenticator app (Google Authenticator, Authy, 1Password…). | Available |
| Sign-in through udiApps | Entry from the udiApps central manager (signed handshake). | Available |
| Corporate SSO (SAML 2.0 / OIDC) | The company's IdP (Okta, Entra ID, Google Workspace). See SSO and SCIM. | Enabled on request |
Development mode
With no auth credential configured in the environment, the instance runs in open dev mode (for local development). In production this is blocked: without Google or credentials, the deploy doesn't report itself healthy (production truth — see Status and limitations).
What it's for#
- Giving each person a unique, auditable identity (the
audit trail records
userEmail). - Requiring a second factor on every account — not just sensitive ones: in the implemented version, MFA is mandatory for any signed-in access.
- Allowing federated entry through corporate SSO (enabled on request) without a local password.
Plan and permissions#
- Sign-in and MFA: all plans.
- SSO/SCIM: from Scale up (enabled on request) — see Plans.
- Who controls it: nobody chooses. In the implemented version, MFA is
mandatory for any signed-in access: signing in without a configured second factor
takes you straight to the MFA setup screen, and there's no way out of it into the
product. Each person sets up their own authenticator; managing people is an
admin/owner action (
member.manage). - There's no "require MFA for a member". The person record has a flag with that name, but it has no effect: no sign-in path reads it. Since MFA is already mandatory for everyone, the flag changes nothing — and it can't be used to exempt anyone.
Step by step — turn on MFA (TOTP)#
Open the MFA setup
In your profile, choose Turn on two-step verification. The platform generates a TOTP secret and a QR code.
Register it in the authenticator app
Scan the QR code (or type the secret) into your app (Google Authenticator, Authy, 1Password, etc.). It starts generating a 6-digit code that changes every 30 s.
Confirm the code
Type the current code to confirm the link. From then on, every sign-in requires your password and the current code.
The TOTP secret is stored encrypted (AES-256-GCM) on the server and never shows up in reports, DSARs, or logs.
Legacy record caveat — the same one stated in Credentials and rotation
Encryption at rest applies to every new record: turning on (or turning on again) MFA writes the seed encrypted. The reader, however, tolerates a legacy plain-text seed: if decryption fails, the stored value is used as is. This exists so as not to break sign-in for people who registered MFA before encryption — and there's no migration that rewrites old records, so "encrypted at rest" describes what is written today, not a retroactive guarantee about every existing record. This is the same caveat as in Credentials and rotation; the two pages used to say different things, and this is the version that matches the code. Turning MFA off and on again rewrites the seed encrypted.
Stating the caveat doesn't claim that a plain-text secret exists in any environment: it says the product still accepts reading one, and that no scan of values was done (nor would one be required) to write this page.
Example#
At Comércio Aurora (fictional), Maria (owner) signs in with Google. João (admin) uses email + password and, because he operates sources and people, turns on MFA. From then on, his sign-in asks for the password and the 6-digit code from the authenticator app.
Expected result#
- A successful sign-in creates the session and takes you to the signed-in area.
- With MFA on, a sign-in without a valid code is denied (you don't get in "with just the password").
- The entry is recorded in the workspace audit trail.
Security#
- Passwords: scrypt hash; the platform never stores or displays the password in plain text.
- MFA: TOTP verification with a tolerance window; secret encrypted at rest in new records, with the legacy-record reading caveat described above.
- Google domain (optional): the owner can restrict social sign-in to a
specific Workspace domain (
hd), rejecting accounts outside it. - Member invitation: registering a person doesn't issue a password. It issues a single-use activation link, with an expiration, stored as a hash; the person sets their own password when accepting (see Users). A lost or expired link is solved by resending the invitation — there's no "generate new password". See Credentials and rotation.
- The team never asks for your password or for the value of a key — see Support.
Limits#
- MFA recovery: it doesn't exist, neither self-service nor through the product. There are no single-use recovery codes, and there's no admin, owner, or support action inside the product that resets another person's second factor — we looked and it doesn't exist in the code. Anyone who loses the authenticator app has no way back through the interface; solving that today requires intervention outside the product. Save the authenticator seed when you set it up.
- Password change: there's no "change my password" screen and no "forgot my password" flow. The sign-in password is set at sign-up; changing it later is a support case. People who sign in with Google or SSO don't have a local password.
- Session: the session is a signed token stored in the browser; the server doesn't keep a list of sessions, so there's no "sign out of all devices" and no session revocation when a credential changes.
- Corporate SSO: stays off until it is enabled for your organization; contact support.
- Transactional email may not be enabled in all current environments; prefer in-app channels when the flow depends on email.
Common errors and how to fix them#
| Symptom | Likely cause | What to do |
|---|---|---|
| Sign-in rejected with the right password | MFA on and code missing/wrong | enter the current code from the authenticator app |
| TOTP code always invalid | phone clock out of sync | turn on automatic time on the device |
| Google rejects the account | Workspace domain restriction (hd) | use an account from the allowed domain |
| "Auth not configured in production" | environment without Google or credentials | the operator must configure the auth envs |
Related#
Last reviewed: 2026-09-17.