Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

(Admin) Add a Create account functionality, as well as the possibility to restrict resource access based on it

Chiusa
  • Qualcosa non va?
#48 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #59 di @gheorghelupu17 — integrata

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php
Ambito
authentication, authorization

Direzione di ricerca

Start by locating the existing public-platform login and sign-up flows, resource access controls, and admin user-management entry points. Trace how user roles and restricted resources are handled, then map the requested approval, rejection, email, and renewal flows against them. Done means the full account lifecycle and role-based access are implemented; the renewal grace period and Terms and Conditions details need clarification.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Visitors should have the possibility to create an account. A non-admin user account can:

  • See the public platform
  • See the resources with restricted access that are associated with their Role
  • Change the email/ password of their account
  • Delete their account

The Admin:

  • Can see and has to approve all user requests
  • Can see all users of the platforms
  • Can only add admin adjacent users (Admin/ Editor), cannot add any other user type
  • Can delete users

When/ If a user account is deleted, they loose access to all materials that were restricted to having an account.

The Log In/ Sign up button should be added back to the public platform. The sign-up form contains the following fields:

  • Nume și prenume
  • Adresa de email serviciu
  • Instituție
  • Persoană de contact/referință, număr de telefon
  • Rol (MAI/ ONG)
  • Sunt de acord cu Termenii și condițiile platformei checkbox

When creating a resource, the levels of access are (several options can be chose simultaneously):

  • Publicul larg (everyone sees it, does not require an account)
  • ONG-uri (does not appear on the public page, can be seen by users with the ONG role)
  • Personal MAI (does not appear on the public page, can be seen by users with the MAI role)

User account creation flow:

  1. The potential user completes the sign up form, which is received by the Admin in a dedicated tab. The Admin also receives an email notification that a new user request was received.
  2. The Admin checks the request and chooses whether to Accept or Reject it.
    - If it is rejected, the account is not created and the potential user receives an automated email that their request was rejected.
    - If it is accepted, the account is created and the potential user receives an automated email that their request was accepted + to set their password.
  3. Once the account is created, the user can see perform the actions described above.

Once created, an account will ba available for 1 year, after which time a renewal request is needed. The user is notified by email that they have to request the renewal of their account, by clicking on the link in the email. The renewal request is received by the Admin, who can approve (=> the account is renewed) or reject it (=> the account is deleted). Eitherway, the user is notified by email of the choice. If the account is not renewed within 1 month (? maybe to long a timeframe), it is automatically deleted. These details also have to be explained in the renewal email and Terms and conditions of the platform.

Lingua principale
PHP
Stelle
0
Fork
0
Merge medio
5h 29m
PR unite (30g)
22

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 code4romania/cpc

Tutte le issue di code4romania/cpc

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.