Make invite-only decide new accounts' role and let admins switch it

Aperta
#9,497 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@aglinxinyuan ci sta già lavorando.

Dal 16/11/2026.

  • #9498 di @aglinxinyuan — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Feature Summary

USER_SYS_INVITE_ONLY only decides whether the browser shows the pending-approval screen. The backend gives every new account INACTIVE whatever the flag says, so with invite-only off a new user signs in to a dashboard where every request is refused (the symptom reported in #7185). The flag is also read once at startup, so changing it means editing the deployment and restarting.

A new account, while invite-only is Now Proposed
off INACTIVE; told to contact an administrator; every dashboard request refused REGULAR; opens the dashboard
on INACTIVE; pending-approval screen unchanged
Proposed Solution or Design
  • Invite-only decides the role a new account starts with: REGULAR when off, INACTIVE until an admin approves it on the Users page when on. This covers local sign-up, the first Google or Apple sign-in, and a sign-up that claims a dataset-contributor placeholder. Accounts already waiting for approval are not promoted.
  • The flag becomes an admin-editable site setting, invite_only, read on every sign-up. Admin → Settings gets a Registration card with an Invite Only switch. USER_SYS_INVITE_ONLY sets the starting value, like the other settings on that page.
  • Invite-only is on by default, because a REGULAR account can run code on the server. Opening sign-up is then a deployment's explicit choice.
  • The sign-up page stops telling users to contact an administrator when their account is already usable.
Affected Area

Deployment / Infrastructure, Other

Lingua principale
Scala
Stelle
333
Fork
202
Merge medio
3g 11h
PR unite (30g)
185

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/texera

Tutte le issue di apache/texera

Issue simili

Altre issue su Scala

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.