In summary we need to enable a user network with push notifications and to integrate a number on handshake protocols to up date both the system data base and Salesforce.
The idea of the backend phase is that to achieve a signup system were either landowners or investors end up in the same role; that role being "standard user". A standard user has access to edit their profile, comment on projects, update their bank account information, review projects they've invested on, manage notifications & update settings and submit projects.
In addition to the "standard user" role there's to be "content editor", “Editor” "Project Owner", "Writer" and "Admin" roles.
The Content Editor role has access to read, edit and create everything on the site except for projects, articles and user roles.
The Project Owner role is to be given to users who create and edit their own projects / investments. In that same manner users who are assigned this role will be responsible of comment threads and updates of their projects/investments.
The Writer Role. Users who are assigned this role are to be able to create and edit their own articles.
The Editor Role. The Editor Role is meant for users who overlook all communications on the site. They are able to edit all content on the site but do not create any content.
The Admin role is assigned to the user responsible of assigning and un assign roles to users as well as re assigning objects among users who share the same roles.
The data to be updated onto salesforce are leads, accounts, opportunities, price lists and products.
Leads are every standard user that exists in the the database who are yet to show real interest in investing. Please have in mind that this user's data bypasses via a two way handshake protocol, one in which the users’ data may be updated from salesforce by a rep, users in higher role or directly by the standard users themselves from their settings or profile page. This means that he field s selected for the protocol are updated on either end of the protocol, the opposite end is to be updated as well. In addition we will include data from the user's’ behavior, such as submitted projects, articles read, comments made, projects they've invested on and maybe others.
Accounts are standard users that have showed real interest in investing. Standard users are unaware that they have become an account. It is important to have in mind that all the data that makes an account comes from the original lead the standard user started out as. Do to experienced investor exercising business from different types of accounts or firms(Joint, Entity or Trust). We have decided to treat accounts as business accounts instead of person accounts for the reason being that we can add different sub accounts and or contacts to said account. These accounts are to be updated onto the existing account via a two way handshake protocol. Just like the lead shared data with the standard user, now the account will share data with the standard user instead of the lead object doing so after being converted.
Price Lists will share data with Projects. As projects are created and updated on the system, Price Lists and products will be created and updated onto Salesforce. Differently from user data, project and product data are a one handshake protocol. This protocol takes place on the system and not on salesforce. Farmshares™ are a specific value at each project level. That being said, Farmshares™ are our products.
Opportunities are where the sales process closes in for the win. Here It is very important to assign the products (Farmshares™) purchased to an account or contact only when the opportunity has been won. This taps into a one way handshake protocol, in which Farmshares™ are to be added to the account and the reflected on two the system for the user to review and follow up on. In the near future said leads in the accounts are to be part of an exchange process.