(Admin) Add a Create account functionality, as well as the possibility to restrict resource access based on it
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- php
- Domain
- authentication, authorization
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- 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.
- 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. - 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.
- Dominant language
- PHP
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 29m
- Merged PRs (30d)
- 22
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from code4romania/cpc
-
(Public) Add a Linii de sprijin card to Acasă, Contact and DesprePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
code4romania/cpc#47 ·
Maintainers usually reply within 1 day
-
(Public) Add Logo + website name to header, footer and FaviconPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
code4romania/cpc#46 ·
Maintainers usually reply within 1 day
-
(Public) Add „Curricule și materiale formări” option to the Tip resursă filterPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
code4romania/cpc#44 ·
Maintainers usually reply within 1 day
-
(Admin) Add all static pages and adjust their way of workingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
code4romania/cpc#51 ·
Maintainers usually reply within 1 day
-
(Admin) Specify file size limit in al content blocs which accept file uploads in the Admin pagesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
code4romania/cpc#50 ·
Maintainers usually reply within 1 day
All issues in code4romania/cpc
Similar issues
-
Difficulty 2/5 Under an hour Newbie friendliness 78/100
opencart/opencart#15763 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
L: github:actions L: php:composer
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dependabot/dependabot-core#16493 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
api-platform/core#8649 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
open-telemetry/opentelemetry-php#2071 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day