I am going to recommend Sugar OS for a small office. They need to have their leads seperated. Sometimes sales people will steal each others leads, I am told. This office is not willing to put up any money right now for Sugar Pro. I suggested a proof of concept installation. Since this rollout will be highly customized I do not want to do seperate installs. It would be too time consuming to modify and admin each seperate instance. So as I see it my options are to try to do seperate databases for each user. I am not sure if this is possible with Sugar OS. I also feel a little funny about this ( I want SugarCRM to suceed wildly) because this is functionality that they could be paying SugarCRM to attain through SugarPro. This next concept may not need to be said, but many people are completely unfamiliar with open source and need to have their hand held throughout the recommendation implementation and adoption phases. It seems the only way to get some people to go down the open source road is through a successful trial.
So my questions are:
Can I run different instances of the db for each user.
Is there another way to do this. Possibly a long term trial of SugarPro Onsite
Maybe SugarCRM would like to offer a long term hosted trial option of Professional to stimulate adotption. This could be something similar to the demo now offered but a seperate instance where it could be customized (admin rights)
Possibly someone would have another suggestion that I have missed?


LinkBack URL
About LinkBacks



Reply With Quote
Bookmarks