Steps to Implement User View Settings

Oct 13, 2025 by wbrum.org 5 views

User View Settings: Enhancing Case Manager Experience

Introduction

As we strive to create a seamless and user-friendly experience for our case managers, it's essential to revisit and refine the settings menu to cater to their specific needs. Currently, when logged in as a case manager, the settings menu redirects to the admin settings page, allowing them to manipulate other user accounts. However, this is not the intended functionality. In this article, we'll outline the necessary steps to implement a customized settings menu for case managers, providing them with access to their own settings only.

Description

The existing settings menu for case managers is not tailored to their specific requirements, leading to confusion and potential security risks. To address this issue, we aim to create a settings menu that allows case managers to update their own information, including their name, phone number, location, password, and email. This menu should be designed to match the Figma design provided, reusing the component created for the admin settings menu.

Steps to Implement User View Settings

To implement the user view settings, we'll follow these steps:

1. Reuse the Admin Settings Menu Component

We'll reuse the component created for the admin settings menu, as it shares the left panel that displays the user's information. However, we'll use the logged-in user's role to determine what appears on the right side of the screen.

2. Update the User's Information

The user's information should be displayed in the panel on the left of the screen using the same component as the Admin Settings Menu. This will ensure consistency and ease of use.

3. Update Password Requirements

When updating their password, the user should be required to enter their old password. This is a security measure to prevent unauthorized password changes. We'll utilize existing functions that handle password changes in Firebase, ensuring a seamless experience.

4. Location Selection

When choosing a new location, the user should be presented with a dropdown list of all available location names, drawn from the DB locations table. This will ensure that the user selects a valid location.

5. Confirm Changes

At the bottom of the page, there should be cancel and submit buttons that prompt the user to confirm their changes. On cancel, all changes should be ignored, and on submit, the changes should be PUT to the backend.

Exit Criteria

To ensure that the user view settings are implemented correctly, we'll follow these exit criteria:

The component matches the Figma design.
The user's information is displayed in the panel on the left of the screen using the same component as the Admin Settings Menu.
Users can update their name, phone number, location, password, and email.
On either save or cancel, the user is prompted with a modal to confirm.
On cancel, no changes are made.
On save, changes are made and reflected in the section on the left that displays their information.

Resources

To implement the user view settings, we'll rely on the following resources:

Figma design: https://www.figma.com/design/sHKYRo824s5Te8qKZeiaAP/%5BCCH%5D-2.-Lo-Fi--%3E-Hi-Fi?node-id=7573-46332&t=Jv1mimH2oOBTLxBh-0

By following these steps and exit criteria, we'll create a customized settings menu for case managers that meets their specific needs and provides a seamless experience.
User View Settings: Q&A

Introduction

As we continue to refine the user view settings for case managers, we've received several questions regarding the implementation and functionality of this feature. In this article, we'll address some of the most frequently asked questions to provide clarity and ensure a smooth implementation process.

Q&A

Q: Why is it necessary to create a customized settings menu for case managers?

A: The existing settings menu for case managers is not tailored to their specific needs, leading to confusion and potential security risks. By creating a customized settings menu, we can ensure that case managers have access to their own settings only, reducing the risk of unauthorized changes.

Q: How will the new settings menu differ from the existing admin settings menu?

A: The new settings menu will reuse the component created for the admin settings menu, but will use the logged-in user's role to determine what appears on the right side of the screen. This will ensure that case managers only have access to their own settings, while admins will continue to have access to all user accounts.

Q: What changes will be made to the password update process?

A: When updating their password, the user will be required to enter their old password as a security measure. We'll utilize existing functions that handle password changes in Firebase to ensure a seamless experience.

Q: How will the location selection process work?

A: When choosing a new location, the user will be presented with a dropdown list of all available location names, drawn from the DB locations table. This will ensure that the user selects a valid location.

Q: What happens when the user clicks the cancel button?

A: When the user clicks the cancel button, all changes will be ignored, and the user will be returned to the previous screen.

Q: What happens when the user clicks the submit button?

A: When the user clicks the submit button, the changes will be PUT to the backend, and the user will be redirected to the previous screen with their updated information.

Q: How will the user's information be displayed in the panel on the left of the screen?

A: The user's information will be displayed in the panel on the left of the screen using the same component as the Admin Settings Menu. This will ensure consistency and ease of use.

Q: What resources will be required to implement the user view settings?

A: To implement the user view settings, we'll rely on the following resources:

Figma design: https://www.figma.com/design/sHKYRo824s5Te8qKZeiaAP/%5BCCH%5D-2.-Lo-Fi--%3E-Hi-Fi?node-id=7573-46332&t=Jv1mimH2oOBTLxBh-0

Conclusion

By addressing these frequently asked questions, we hope to provide clarity and ensure a smooth implementation process for the user view settings. If you have any further questions or concerns, please don't hesitate to reach out.

Additional Resources

Figma design: https://www.figma.com/design/sHKYRo824s5Te8qKZeiaAP/%5BCCH%5D-2.-Lo-Fi--%3E-Hi-Fi?node-id=7573-46332&t=Jv1mimH2oOBTLxBh-0