How can I share a lead's information with an Account?

We are a manufacturer that only sells to third-party authorized dealers. We still do our own marketing and collect leads on behalf of our dealers. We normally forward the contact information of a lead to the appropriate dealer. Now that we are using SugarSell, I am having a hard time sending the dealers the lead's contact information. Dealers do not have a Sugar account. When I go to the leads contact card and select "Share" it only sends a link that requests a username and password. Is there another way?

Parents Reply
  • Enabling other modules into Portal, even custom ones, is possible without custom code if the module has a relationship to either Accounts or Contacts and if such a relationship is the enough to fetch data properly.

    In case criterias to load data from other modules into Portal is not that simple, then it is possibile to implement a specific Visibility Strategy for that module in Portal.

    André Lopes
    Lampada Global
    Skype: andre.lampada
  • Hi and , I am still not sure how to enable other modules for the portal without custom code. Can you tell me how you added those modules there and if they are actually accessible in the portal when enabled? I must be missing something. Slight smile

  • is totally right about:

    custom extension (to enable portal visibiility)

    $dictionary['Class']['portal_visibility'] = [
        'class' => 'Module',
        'links' => [
            'Accounts' => 'accounts_link',
            'Contacts' => 'contacts_link',

    and custom view (to enable configuring record and list view for Portal). Custom views must be placed inside core module (modules/Module/clients/portal/views/) in order to let Studio realize that module is portal enabled.

    Additionally you have to enable that module into Role "Customer Self-Service Portal Role".

    Finally you have to run QRR and Repair Roles.

    You will be able to modify the views record and list of that module for Portal. Mind you also need to move the target module from tab "Hidden Modules" to "Displayed Modules".

    On authenticating with a valid Portal User you will be able access that module accordingly.

    Portal platform is "almost" as flexible as base platform is.

    We had implemented pretty amazing features for some customers, like:

    • Filters
    • Custom dashlets
    • Modules dashboards
    • Subpanels
    • Readonly Reports built in the base platforms
    • Dynamic and wizard layout for Cases create view
    • Custom and complex Portal Visibility Strategies

    In short words, it is possible to evolve the Customer User experience, leveraging relationships.

    André Lopes
    Lampada Global
    Skype: andre.lampada
  • Thanks ,

    One minor improvement, I would make sure to put the view(s) to the custom module's "custom/modules/Module/clients/portal/views" not on the core directory.



    Enrico Simonetti

    Senior Manager, Integrations Development

    SugarCRM Inc

  • So this is a new improvement on version 11.1, because previous versions required portal folder inside core module instead!

    That is a great news!

    André Lopes
    Lampada Global
    Skype: andre.lampada
  • , this is indeed odd.

    Unless something has changed since version 9.2 where the portal changed implementation (which I did contribute to, personally), that was one of the changes I have implemented to allow the use of the custom folder only.

    You could use this linux diff/patch, which I used at the time (2 years ago as you can see from the gist creation date), to test the addition of a new fully visible Sugar module:

    Obviously you would need the module in there first, and also the permissions correctly set on the Portal role.

    Feel free to test and confirm, if this is still applicable today though!



    Enrico Simonetti

    Senior Manager, Integrations Development

    SugarCRM Inc