Three ways in — and none replaces another
A password, your media server account, or a sign-in service you already run. Nexview does all three at once, and a new way never takes an old one away: if you want to keep your password, you keep it.
What appears on the sign-in page is your decision
Out of the box there is exactly one field for the username and one for the password. Everything else appears only once you set it up — with nothing configured, the page looks exactly as it always did.
Connect a media server and a “Sign in with Plex” button appears (or Jellyfin, or Emby). Add sign-in providers and each one adds a further button, carrying the name you gave it.
Every one of these ways leads into the same account. Role, quota, permissions and history hang off the Nexview account, not off the way in.
Authentik, Keycloak, Pocket ID, Google — or whatever else you run
OpenID Connect is a standard, which is why there is no list of supported providers here. From Nexview's point of view a provider is three values: address, client id, secret. Whether Authentik, Keycloak, Pocket ID or Google sits behind them makes no difference.
You do not enter the individual endpoints — Nexview reads them itself from the provider's /.well-known/openid-configuration. The scopes requested are openid email profile, nothing more.
What your provider needs from you is the redirect URI. Nexview builds it from your public address and shows it ready to copy:
https://your-nexview-address/api/auth/oidc/<slug>/callback⚠️ The public address has to be right first. A provider rejects any redirect URI that is not registered with it exactly — which is why Nexview says up front that it should be set first. If Nexview runs under a sub-path, the sub-path belongs in it.
Setup guides for Authentik, Keycloak, Pocket ID and Google are in the README — four lines each, naming the actual menu items of each service.
Linking, not replacing — and two switches worth understanding
You link an existing account in your own profile under Sign-in. Afterwards both work: the provider's button and still your password. The link can be undone in the same place.
New people can be created automatically if you flip the switch — they get the role and quota from your defaults. Leave it off and only people you have invited get in.
⚠️ With Google and Microsoft, “create automatically” means literally: every person who has an account there. Those providers hand out an email address to half the world. The switch belongs on only if you decide yourself who has an account at the provider — or if you have restricted the application there to your own organisation. Nexview writes exactly that next to the switch, not into a manual.
The enabled switch takes a provider off the sign-in page without throwing the configuration away — the right move while something is being rebuilt at the provider's end. And a single identity can be blocked without disabling the whole provider.
With your media server account
If you already run a media server, the accounts exist there — and do not have to be created a second time in Nexview. Plex, Jellyfin and Emby all work, including at the same time.
The link does more than sign you in: it is how Nexview knows what is already in your library, and who has already watched which title.
In full on the Media servers page.