Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#48 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@gheorghelupu17 がすでに取り組んでいます。

2026年10月7日 から。

  • #59 @gheorghelupu17 による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
php
領域
authentication, authorization

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
PHP
スター
0
フォーク
0
平均マージ
5時間 29分
マージ済み PR（30日）
22

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

code4romania/cpc のほかの issue

code4romania/cpc の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。