changes from bot review

Author: gantoine

docs/Navigation.md

@@ -34,6 +34,7 @@ search:
         - [Keycloak](administration/oidc/keycloak.md)
         - [PocketID](administration/oidc/pocketid.md)
         - [Zitadel](administration/oidc/zitadel.md)
+        - [VoidAuth](administration/oidc/voidauth.md)
     - [Scanning & Watcher](administration/scanning-and-watcher.md)
     - [Scheduled Tasks](administration/scheduled-tasks.md)
     - [Server Stats](administration/server-stats.md)

docs/administration/index.md

@@ -16,7 +16,7 @@ The end-user equivalent (how to actually play the games, build collections, uplo
 - **[Users & Roles](users-and-roles.md)**: roles, the scope model, how permissions add up
 - **[Invitations & Registration](invitations-and-registration.md)**: invite links, public signup, first-user setup
 - **[Authentication](authentication.md)**: session config, password reset, Client API Tokens for devices
-- **[OIDC Setup](oidc/index.md)**: Authelia, Authentik, Keycloak, PocketID, Zitadel, SSO + role mapping
+- **[OIDC Setup](oidc/index.md)**: Authelia, Authentik, Keycloak, PocketID, Zitadel, VoidAuth, SSO + role mapping
 
 ### Content & library
 

docs/administration/oidc/index.md

@@ -5,7 +5,7 @@ description: Wire up to an OpenID Connect provider for SSO and centralised user
 
 # OIDC Setup
 
-OpenID Connect (OIDC) lets users sign in through an external identity provider: Authelia, Authentik, Keycloak, PocketID, Zitadel, Okta, Auth0, or anything standards-compliant. Single sign-on across your homelab, no app-specific password to manage, centralised MFA, and map OIDC groups/claims to roles.
+OpenID Connect (OIDC) lets users sign in through an external identity provider: Authelia, Authentik, Keycloak, PocketID, Zitadel, Okta, Auth0, VoidAuth, or anything standards-compliant. Single sign-on across your homelab, no app-specific password to manage, centralised MFA, and map OIDC groups/claims to roles.
 
 <!-- prettier-ignore -->
 !!! note "OIDC is optional"
@@ -28,6 +28,7 @@ Pick your provider and follow the step-by-step instructions. They all end with t
 - [Keycloak](keycloak.md)
 - [PocketID](pocketid.md)
 - [Zitadel](zitadel.md)
+- [VoidAuth](voidauth.md)
 
 Not listed? Most standards-compliant OIDC providers work: Okta, Auth0, Google Workspace, Microsoft Entra, etc. Use one of the above as a template and consult your provider's docs for the registration side.
 
@@ -38,7 +39,7 @@ Whichever provider you pick, set these in the `romm` service's environment:
 ```yaml
 environment:
     - OIDC_ENABLED=true
-    - OIDC_PROVIDER=<authelia|authentik|keycloak|pocketid|zitadel|generic>
+    - OIDC_PROVIDER=<authelia|authentik|keycloak|pocketid|zitadel|voidauth|generic>
     - OIDC_CLIENT_ID=<from your provider>
     - OIDC_CLIENT_SECRET=<from your provider>
     - OIDC_SERVER_APPLICATION_URL=https://auth.example.com

docs/administration/oidc/voidauth.md

@@ -14,7 +14,7 @@ Your RomM instance will be referenced as https://demo.romm.app .
 
 ## 2. Create a new app
 
-Login as an admin in VoidAuth web interface. Create a new OIDC Apps  (e.g. `RomM`). 
+Login as an admin in VoidAuth web interface. Create a new OIDC Apps (e.g. `RomM`).
 
 - **Name**: `RomM`
 - **Home Page URL**: `https://demo.romm.app`