You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM, anyone can create an account and access all the sensitive information of all of CCH and its clients so we want to update the process of how a new account can be created
You will be adding a feature that lets admins add new accounts via their settings menu
Steps
Implement the features of the Add Account Button on this page Figma
When Clicked it should take you to a page almost identical to this figma
Just a few small changes since this specific design is for editing the account, but we will repurpose it to creating a new account:
Add a title that says either "Invite New Admin User" or "Invite New Case Manager" <-- the account type that is being added is determined by the tab that is selected on the original page
You can ignore the "About" subtitle
Keep the Email input box, this should then be posted to the backend users table (the only information you have is email and account type so create a new POST route in users.ts that handles this specific POST request that only inserts email and account type (account type is called role in the DB)
when clicked, inviting this user also sends them an invite link via nodemailer
Case managers should be inserted as users and Admins should be inserted as admins3. Now that admins can add new accounts make sure that only added emails can create new cm and admin accounts
be sure to double check that an email added for a cm account cant create an admin account and an email added for an admin account cant create a cm account
The text was updated successfully, but these errors were encountered:
Description
Steps
users
table (the only information you have is email and account type so create a new POST route inusers.ts
that handles this specific POST request that only inserts email and account type (account type is called role in the DB)The text was updated successfully, but these errors were encountered: