Basic CRM

Basic web-based CRM system ## Deliverables Hi, I am looking at getting a basic CRM built please find the details below Database schema Group The group table will contain information about a group of people. e.g. a group may have a GroupName such as "Admin users" and the description may be "These users have administration rights throughout the network" ================ GroupID GroupName GroupDescription GroupRights (This will be a short int and will indicate what rights a group has; For the scope of this project this will either be a 0 or a 1 but may need other numbers at a later date) AdminUser The AdminUser table will contain information about users of the system who will login and add / edit update leads, add / edit groups, add / edit person details. A person can be associated with one to many groups hence the reason for the table AdminUserGroup* ================ AdminUserID UserName Password FirstName LastName EmailAddress PhoneNumber AdminUserGroup* This table is used for the many to many relationship between a group and an AdminUser (One AdminUser can belong to many Groups) ================ AdminUserID (This is the foreign key of the AdminUser table AdminUserID) GroupID (This is the foreign key of the GroupTable) Person The Person table is used to store information about users who will have leads associated with them by an Admin user. ================ PersonID FirstName LastName CompanyName StreetAddress City State ZipCode Country PhoneHome PhoneWork MobilePhone EmailAddress Lead The Lead table contains information about a lead. A lead is associated with a Person (See Person table) as well as with the Admin user who entered the lead (See AdminUserTable) ================ LeadID LeadTitle LeadDescription LeadStatus (Can be one of three options, Open, Closed, On hold) LeadDueDate AdminUserID (This is the foreign key of the AdminUser table AdminUserID) PersonID (This is the foreign key of the Person table) LeadHistory The LeadHistory table will be used by Admin users to make notes about a Lead. ================ LeadHistoryID LeadID (This is the foreign key of the Lead table attribute LeadID) AdminUserID (This is the foreign key of the AdminUser table AdminUserID) HistoryNotes LeadDocument The LeadDocuments table will be used to store documents (PDF files, Word documents etc) which are associated with a lead. ================ LeadDocumentID LeadID (This is the foreign key of the Lead table attribute LeadID) DocumentTitle DocumentDescription Document (This will probably be a BLOB object in the database) DocumentUploadedBy Workflow ================ An admin user will login via a Login/ Password page Once successfully authenticated one of two things will happen. if the user is a member of a group who has a GroupRights attribute of 1 (For the rest of this document we will call these users POWERUSERS) then they will be able to see 1) A list of all the AdminUsers and their associated Leads grouped by AdminUsers 2) A list of the leads associated just to them Note: Any leads which have a LeadDueDate of less then the currentdate (Leads which are past due should appear in red). Leads which are due within the currentweek should appear in yellow. If the user is a member of a group who has GroupRights <> 1 (Not a POWERUSER) then they will only see leads associated with them and not anyone else after they login. Again, leads which are due or overdue should appear in either red or yellow as mentioned above. POWERUSERS Should be able to add/ edit / delete * Groups * AdminUsers * Re-assign Adminusers to Groups * Person * Leads * Re-assign Persons to leads (Note if a person is re-assigned to an EXISTING lead a new entry should be created in the LeadHistory table saying that the lead has been reassigned) * LeadHistory * LeadDocuments * In a nutshell, POWERUSERS should be able to do anything to any record in the entire application and any document(s) associated with that record. Non POWERUSERS As previously mentioned should only be able to view leads associated with them. * Only able to edit existing leads (Expect for re-assigning the lead to another person) associated with them. * Able to add/ edit/ delete documents associated with the Lead * Able to add/ edit but NOT DELETE history records associated with a Lead which is assigned to them * Not able to add/ delete/ create leads, groups, persons Notes: Must be developed using MSSQL 2005 and ASP.NET 2.0 VisualStudio 2005 C# Must be very Web 2.0 looking and use the ASP.NET AJAX control kit where-ever possible <http://www.asp.net/ajax/ajaxcontroltoolkit/samples/> ****I will create the back-end database and build the business objects using NETTIERS 2.2 and CodeSmith 4.0.**** It will be your job to create the above functionality and requirements using the entities created by .NETTIERS 2.2 and CodeSmith 4.0 Any changes to the Database schema/ Entities should be able to be re-built using NETTIERS 2.2 and CodeSmith 4.0. CSS design not required but layout must be intuitive between screens Any third party components used within the website must be free and include all source code ## Platform MSSQL 2005 and ASP.NET 2.0 VisualStudio 2005 C# / AJAX