Sugar Portal

Hi Brianna Burke

Definitely it is possible to accomplish with some upgrade safe and packageScan safe customizations. Indeed we had implemented exactly that for a customer.

Can you give me more information about these customizations?

I agree it is not currently possible, more due to the fact that one Contact in Sugar (for how it works and it is structured) is supposed by default to be related only to one Account at the time.

It is definitely possible to extend and customise the portal visibility model since version 9.2, but it is indeed quite technical.

In specific to extend the Cases visibility one should look at data/visibility/portal/Cases.php (which should be extended in the equivalent custom directory) in addition to an extension to the Case's vardefs definition specifically in this area, to point to the extended visibility file:

    'portal_visibility' => [
        'class' => 'Cases',
        'links' => [
            'Accounts' => 'accounts',
            'Contacts' => 'contacts',
        ],
    ],

More information on how to extend the portal functionality can be found on other threads, specifically here:

• https://sugarclub.sugarcrm.com/dev-club/b/dev-blog/posts/adding-a-custom-module-to-the-customer-portal
• https://sugarclub.sugarcrm.com/dev-club/f/questions-answers/3837/displaying-built-in-modules-to-customer-self-service/18879#18879 

Be mindful that extending the visibility opens up the opportunity of making a mistake and showing more data than supposed to as well. It needs to be tested throughly before applying it to any production environment.

Hopefully it helps to extend the current functionality the way you want it to work

I agree it is not currently possible, more due to the fact that one Contact in Sugar (for how it works and it is structured) is supposed by default to be related only to one Account at the time.

It is definitely possible to extend and customise the portal visibility model since version 9.2, but it is indeed quite technical.

In specific to extend the Cases visibility one should look at data/visibility/portal/Cases.php (which should be extended in the equivalent custom directory) in addition to an extension to the Case's vardefs definition specifically in this area, to point to the extended visibility file:

    'portal_visibility' => [
        'class' => 'Cases',
        'links' => [
            'Accounts' => 'accounts',
            'Contacts' => 'contacts',
        ],
    ],

More information on how to extend the portal functionality can be found on other threads, specifically here:

• https://sugarclub.sugarcrm.com/dev-club/b/dev-blog/posts/adding-a-custom-module-to-the-customer-portal
• https://sugarclub.sugarcrm.com/dev-club/f/questions-answers/3837/displaying-built-in-modules-to-customer-self-service/18879#18879 

Be mindful that extending the visibility opens up the opportunity of making a mistake and showing more data than supposed to as well. It needs to be tested throughly before applying it to any production environment.

Hopefully it helps to extend the current functionality the way you want it to work