Build web dashboard, React + .NET/ASP.NET + MongoDB
Budget: $250 – $750 USD
Hello,
I need a web dashboard to go along with my mobile application. I will split the job into multiple parts. The stack used will be React + .NET + MongoDB.
The first part will consist of an authentication system with layers and parent controls. There should be different types of accounts. The first type of account will be admin; this type will be able to manage all other accounts. The first account type that is not admin is called "TOP" this account will have children of type "NATIONAL." The top-level account can manage their children and their children, which is called "LOCAL." The "NATIONAL" accounts can manage their children, which will be of type "LOCAL." All accounts can manage themselves, and no account can manage its parent. Any account with possible children ("TOP," "NATIONAL") can have multiple children of their children type (TOP -> NATIONALS, NATIONAL -> LOCALS). Admins can create an account of any type and manage their relations. Important to note that an account can never have more than one parent. TOP-level accounts can create any account of their accepted children types (NATIONAL, LOCAL). But, these creations will be created as requests that admins must accept before they are created. The NATIONAL level account can create children of type LOCAL, but once again, they must be accepted by an admin. The admin can delete any type of account, and other accounts can request the deletion of any of their children (if they have any) and their children (if they have any).
Accounts can then be logged onto by using the credentials that the admin or parent created along with the account. When logged in, the controls will depend on the account type (remember what they could and couldn't manage.) An admin must accept any account edits that an admin does not make.
It is recommended to make the controls as modular as possible to be reused within different types of dashboards.
This will be the first part; I hope to find someone that will be able to take the rest of the parts to the goal as well.
When it comes to style, we expect a clean-looking, minimal design. Dashboard controls are at focus; therefore, a component library like Blueprint is to be recommended. We have our primary color and an abstract logo that we will supply you; the name is classified as of yet, so use a placeholder title. I'd be happy to discuss any details further.
I need a web dashboard to go along with my mobile application. I will split the job into multiple parts. The stack used will be React + .NET + MongoDB.
The first part will consist of an authentication system with layers and parent controls. There should be different types of accounts. The first type of account will be admin; this type will be able to manage all other accounts. The first account type that is not admin is called "TOP" this account will have children of type "NATIONAL." The top-level account can manage their children and their children, which is called "LOCAL." The "NATIONAL" accounts can manage their children, which will be of type "LOCAL." All accounts can manage themselves, and no account can manage its parent. Any account with possible children ("TOP," "NATIONAL") can have multiple children of their children type (TOP -> NATIONALS, NATIONAL -> LOCALS). Admins can create an account of any type and manage their relations. Important to note that an account can never have more than one parent. TOP-level accounts can create any account of their accepted children types (NATIONAL, LOCAL). But, these creations will be created as requests that admins must accept before they are created. The NATIONAL level account can create children of type LOCAL, but once again, they must be accepted by an admin. The admin can delete any type of account, and other accounts can request the deletion of any of their children (if they have any) and their children (if they have any).
Accounts can then be logged onto by using the credentials that the admin or parent created along with the account. When logged in, the controls will depend on the account type (remember what they could and couldn't manage.) An admin must accept any account edits that an admin does not make.
It is recommended to make the controls as modular as possible to be reused within different types of dashboards.
This will be the first part; I hope to find someone that will be able to take the rest of the parts to the goal as well.
When it comes to style, we expect a clean-looking, minimal design. Dashboard controls are at focus; therefore, a component library like Blueprint is to be recommended. We have our primary color and an abstract logo that we will supply you; the name is classified as of yet, so use a placeholder title. I'd be happy to discuss any details further.