Sign-in, account and OTP
The portal is at admin.llm.netter.io. Documentation is public; operations on account data require an authenticated session.
Register and sign in
- Open Create account or Sign in.
- Use email and password, or Google when that button is available.
- Complete email verification, password updates and profile details when requested.
- If you do not belong to a company yet, complete company registration or accept your administrator's invitation.
A Google identity with verified Gmail or Workspace claims may avoid a second Netter email confirmation. Other cases retain the required verification. A verified email address does not establish authority to represent a company.
Where the one-time code comes from
The OTP is generated by the authenticator app linked to your account. It is separate from your password and is not sent by email.
| What the page shows | What to do |
|---|---|
| A QR code for authenticator setup | Add an account in your authenticator, scan the QR code and enter the current code |
| Only a code field | Open the authenticator already linked to that account and enter its current code |
| Code rejected | Check the account and automatic device time; try a fresh code before it expires |
| Authenticator unavailable | Ask a Netter administrator for account recovery; identity verification precedes a reset |
Do not send QR codes, setup secrets, passwords or OTP codes in support tickets.
Optional second factor
OTP enrollment is optional. Once enabled, the code is required for both password and Google sign-ins. Google sign-in preserves the Netter second factor already enrolled.
Open Account in the user menu to manage password and authentication. The initial portal administrator and the identity console administrator are separate accounts. There is no public administrator password.
Forgotten password or expired session
Use password recovery on the sign-in page. If the message does not arrive, check spam and the email address used at registration. An expired portal session requires another sign-in; an API key cannot replace that session.
If Google sign-in fails on return, record only the error message and time. Do not share the full callback URL, which may contain authorization codes and authentication state.