[FEATURE]Idea flow related to Adding Admin feature #5

[preranah7]

Hi ,I am interested in solving this issue. Here what we can do is edit the user model containing email and role. Role can have two values : user and admin. (The roles will not get asked during the signup form filling, default value will be user) To make the role as admin, the maintainer/admin of the site should be the first to register/signup Through mongoose it is possible and I would like contributing to implement this logic, if there is a single maintainer/admin. While authorizing, we can give the user who owns the camp information card and user with role : admin ,access for edit and delete buttons. Kindly let me know if there are multiple admins/maintainers. Thankyou. Issue #5

[Vignesh025]

Hi @preranah7 ,

Thank you for your interest in solving this issue and for the detailed proposal. Your approach aligns well with what we are looking for, particularly the logic around assigning roles and authorizing actions like edit and delete.

However, we require the admin feature to support multiple administrators. If you have any suggestions on how this could be extended to accommodate multiple admins while retaining the core functionality, we would greatly appreciate your input.

Thank you again for your contribution, and I look forward to hearing your thoughts.

[preranah7]

For multiple admins suggested workflow is

• to make a admin panel
• the earlier approach discussed will be the same for one admin
• If any other person wants to be admin he/she will send the mail to the original admin(first admin),containing their email
• A page named admin.js will get render only to admins(initially to the first admin) asking for the email to make other person admin
• The email will get searched in database and their role will be changed from user to admin. -In the UI or footer we can provide the email of the original admin so that other maintainers/admins can send the mail. Please review this approach. I can raise the following PRs 1)To make changes in user schema and and write the logic for the first admin 2)To create a admin.ejs page which will only get rendered to the users who contain role as admin and the page will have a form where email/username of the person you want to make admin will be asked. 3)To search the query in the database and change the role to admins. 4)Making the UI of the page understandable, easy to use and follows the color palette. Authorize the admins for deleting and editing the camps listings. Thankyou.

[Vignesh025]

Hey @preranah7 ,

Let's proceed with the idea of adding the role field in the schema, with "user" as the default value. This role can be updated by the first admin directly through the database.

For the roles, the permissions should be structured as follows:

User:

• Can view and add reviews to any campgrounds
• Can add new campgrounds
• Can edit/delete their own campgrounds

Admin:

• Can view, edit, and delete any campground
• Can add new campgrounds
• Can remove any review

This should give us a clear distinction between the two roles and the permissions they hold.

Looking forward to seeing your implementation!

[preranah7]

Sure @Vignesh025. Thankyou.