We would like to develop a standalone app and sell it to non-salesforce.com customers. We plan to use Force.com platform and OEM embedded licences. Our app is intended for professionals so most of our users will buy only 1 license ( and will be using own separate ORG).
Issue: Access to many unavailable features may cause low user adoption.
OEM licence gives access only to Accounts, Contacts and custom objects. First user in every org must have a system admin profile which cannot be customized. It means that each customer will get a System Admin profile and access (in most cases - read only) to all CRM features in setup.
Setup section cannot be customized or overwritten by VF.
As user adoption is one of the most important factors having impact on customer's success, we are afraid that our customers will be confused and frustrated of having multiple features that are unaccessible for them. Have any of you faced similar problem? How did you manage to solve it?
We would like to develop a standalone app and sell it to non-salesforce.com customers. We plan to use Force.com platform and OEM embedded licences. Our app is intended for professionals so most of our users will buy only 1 license ( and will be using own separate ORG).
Issue: Access to many unavailable features may cause low user adoption.
OEM licence gives access only to Accounts, Contacts and custom objects. First user in every org must have a system admin profile which cannot be customized. It means that each customer will get a System Admin profile and access (in most cases - read only) to all CRM features in setup.
Setup section cannot be customized or overwritten by VF.
As user adoption is one of the most important factors having impact on customer's success, we are afraid that our customers will be confused and frustrated of having multiple features that are unaccessible for them. Have any of you faced similar problem? How did you manage to solve it?
