Create a Database with various levels of secure access

I need a database built that will accept data from a web form. The database will need to be accessible online and have 5 levels of access: 1. Administrator 2. Account Executive 3. Merchant 4. Sub Merchant 5. Sales Agent 6. Provider The web form will contribute data that will match 24 unique fields: Access to the database would be through a secure website portal. The access would be determined by the user name (probably the email address) and a password determined by the user. The levels of access would look like this: **Administrator: ** Administrator would have total access to all areas and would be able to determine what fields that would be used for each account. There would be a default for all fields except Unique Account ID # which would be optional. Admin would also determine what fields would be available for the reports on the report screen. **Account Executive:** Account Executive would have access to all fields except customer data for all merchant accounts within his jurisdiction (as determined by Admin) **Merchant:** Merchant has access to all fields for its customers. Merchant access would include all data within the merchants database. **Sub Merchant:** Sub merchant would have access to all data within its sub merchant database but not the data for other sub merchants within the merchants database. **Sales Agent: ** Sales agent has access to all data within sales agent customer database but not the data for other sales agents within the sub merchant's database. **Provider: ** Provider would have access to all fields in database for product they provide. The provider would not have access to any product data they are not assigned access to by the administrator. ## Deliverables I need a database built that will accept data from a web form. The database will need to be accessible online and have 5 levels of access: 1. Administrative 2. Account Executive 3. Merchant 4. Sub Merchant 5. Sales Agent 6. Provider The web form will contribute data that will match 24 unique fields: Access to the database would be through a secure website portal. The access would be determined by the user name (probably the email address) and a password determined by the user. The levels of access would look like this: Administrative: Administrative would have total access to all areas. The administrative would be able to determine what fields that would be used for each account. There would be a default for all fields except Unique Account ID # which would be optional. Admin would also determine what fields would be available for the reports on the report screen. Account Executive: Account Executive would have access to all fields except customer data for all merchant accounts within his jurisdiction (as determined by Admin) Merchant: Merchant has access to all fields for its customers. Merchant access would include all data within the merchants database. Sub Merchant: Sub merchant would have access to all data within its sub merchant database but not the data for other sub merchants within the merchant's database. Sales Agent: Sales agent has access to all data within sales agent customer database but not the data for other sales agents within the sub merchant's database. Provider: Provider would have access to all fields in database for product they provide. The provider would not have access to any product data they are not assigned access to by the administrator. The database would have the ability to be searched by phone number and/or merchant number. Form for setting up new accounts for database would include the following fields: 1. Corporate Name 2. Corporate Address 3. Corporate City 4. Corporate State 5. Corporate Zip 6. Corporate Phone Number 7. Tax ID # 8. Contact #1 Name 9. Contact #1 Title 10. Contact #1 Phone 11. Contact #1 Email address 12. Contact #2 Name 13. Contact #2 Title 14. Contact #2 Phone 15. Contact #2 Email address 16. Bank or Institution Name 17. Bank or Institution Address 18. Bank or Institution City 19. Bank or Institution State 20. Bank or Institution Zip 21. Bank or Institution Routing # 22. Bank or Institution Account # 23. Voided Check Upload Button (for uploading files to system) 24. DBA Name 25. DBA Address 26. DBA City 27. DBA State 28. DBA Zip 29. Contact #1 Name 30. Contact #1 Title 31. Contact #1 Phone 32. Contact #1 Email address 33. Contact #2 Name 34. Contact #2 Title 35. Contact #2 Phone 36. Contact #2 Email address 37. Account Executive Name Each new merchant would be assigned a unique Account ID # created by the database. Reports would be available for each level of access. The fields available for reporting would be assigned by admin when accounts are set up. Example of what reports might look like: Administrator Administrator will be able to pull reports for all fields and all account holders. Account Executive: Account Executive would have real time access to the report screen. Account Executive would have access to all product related sales data but not any of the customer info. Account Executive would not be able to see other Account Executive's sales data. Merchants Reports: Merchants would have real time access to the report screen. All fields for all sales. Report can be organized by Sub Merchants and Sales Agents Sub Merchants: Sub Merchants would have real time access to the report screen. All fields for all sales. Reports will only report data for Sub Merchants accounts. Sales Agents: Sales Agents would have real time access to the report screen. But only limited fields as determined by Merchant and Sub Merchant and only the data for Sales agent own customers, not any of the other Sales Agents within the database. Provider: Providers would be able to review and all data for any customer that bought their product. They would not be able to see the other products sold unless they were given permission to from the Administrator. Additionally I will need a basic web portal created for user access. The portal does not need to be fancy since it will be for approved and credentialed users of the product. The web site needs to be easy to modify from the back end in terms of look and adding pages etc. The form used for gathering data for the database will also need to be created and hosted in the website once the user logs in. The form is a data intake for setting up a policy. The policy needs to look like the attached forms and can be a printable web form or a pdf, preferably a pdf. The form will have one area that will be unique to the form and that area will contain their unique policy number. I added a big black arrow on the policies to show you where the customization will need to go. That will most likely be a merge field from the database. The policies are non-enhanceable but for specific reasons the policy can be cancelled by the issuer within 7 days of issue. These cancelations will need to be approved by me so I want an email to come to me once someone requests a cancelation of the policy. The email will show the reason for the cancelation and a button that says approve or reject. Once I press approve or reject the policy will either be canceled or there will be no change. An email will automatically go out and notify the issuer of the disposition of my action (cancelled or rejected). The administrative back end of the database and website needs to accessible on my android cell phone if possible. The policy once it is issued from the web form I want a confirmation email to go to the issuer to acknowledge it was successful or unsuccessful if that is the case.