[Vtigercrm-developers] Interested? Multiple Portals with different permissions

Tony Sandman tonysandman999 at gmail.com
Thu Jun 20 13:04:57 GMT 2019


Can we make it easier and faster with: opencollective.com or so?

T.

On Thu, Jun 20, 2019 at 6:02 PM nilay khatri <nilay.spartan at gmail.com>
wrote:

> Hi Prasad,
>
> Yes that's the idea with un-marrying portal config from contacts.
>
> In vtiger 7 portal does not use SOAP.
>
> I am more inclined towards implementing Open Source solution and making
> this a part of official Vtiger Open Source.
>
>
> On Thu, Jun 20, 2019, 4:19 PM S T Prasad <stprasad at stprasad.com> wrote:
>
>> Hi Nilay,
>> We have also worked extensively on the Portal concept and customization,
>> and dont like to link it solely with Contacts. Employees, Vendors etc could
>> be some others. I like the idea of un-marrying the Portal away for
>> Contacts, it would provide more variety.
>> We have also integrated with some client requested APIs which they wanted
>> to provide to their Portal Users.
>>
>> Also, moving away from SOAP could be considered, perhaps using pure
>> Webservices?
>>
>> More as we progress
>> With best regards,
>>
>> S.T.Prasad (Skype: stprasad at stprasad.com)
>> Founder and Chief Shikari
>> http://www.vtigress.com
>> The Purr-fect mate for vTiger
>> Certified Solution Partner for Asia and Africa
>>
>>
>> On Thu, Jun 20, 2019 at 1:59 PM nilay khatri <nilay.spartan at gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> there is a thread with some discussion on Open Source solution for
>>> multiple portals.
>>>
>>>
>>> We have been thinking about this and have come up with following
>>> approach to start with:
>>>
>>> 1. A setting page where admin user can define various types of portals.
>>> This would be an enhancement to the existing Portal configuration module.
>>> With a change that user can now define multiple portal configurations and
>>> define a Unique Name for each of them.
>>> 2. Separate the Portal fields from Contacts module into a Separate
>>> module (Entity type). Which would act as a Junction between Contacts and
>>> Various Portals.
>>> So basically 1 record per contact per portal.
>>>
>>> The advantage here is:
>>> - we can have a field in contacts module such as Type/Category. based on
>>> the type a Contact could be automatically assigned access to portal via
>>> workflows.
>>> - we can create multiple portals with a different set of access such as
>>> for Project, Referrals, Support etc.
>>> - requires minimal code changes
>>> - gives more control on which user can give access to portals, as the
>>> Junction module would be an entity module
>>>
>>> Feedback, Opinion?
>>>
>>> Are you interested to contribute?
>>>
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>
>> _______________________________________________
>> http://www.vtiger.com/
>
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20190620/4d27dfd3/attachment.html>


More information about the vtigercrm-developers mailing list