Data segregation on portal

[abhilash.kumar.niit]

Hi,

i have created portals on ESPO crm say
Portal 1
Portal 2

now i have some data in portal 1 and some data in portal 2. all the data is available in all portal can i make data portal specefic?

[yuri]

Hi,

It requires a bit of coding.

Example for KB Article that uses the Portal field:

https://github.com/espocrm/espocrm/blob/9.0.8/application/Espo/Modules/Crm/Resources/metadata/selectDefs/KnowledgeBaseArticle.json#L6

https://github.com/espocrm/espocrm/blob/9.0.8/application/Espo/Modules/Crm/Classes/Select/KnowledgeBaseArticle/AccessControlFilters/Mandatory.php

[abhilash.kumar.niit]

Hi,
i am not able to create a relation with the portal is there any other way to implement this?

[PavelZ]

May I ask if there are any plans to address this issue in a future ESPOCRM update, perhaps by allowing it to be configured through admin settings?

[abhilash.kumar.niit]

Do i need to do code for all the objects? or is there any possibility to apply it across all the objects/data?

[yuri]

I think yes. You can have the same class but define it in metadata for every needed entity type.

[IshitaRana]

Hi,

I’m trying to implement portal-specific access control for the Case entity in EspoCRM, similar to how it’s done for KnowledgeBaseArticle (as seen in Espo\Modules\Crm\Classes\Select\KnowledgeBaseArtic le\AccessControlFilters\Mandatory).

In the KnowledgeBaseArticle implementation, a relation like knowledgeBaseArticle_portal is used to filter records based on portalId. However, in my case, I’m unable to create any link (relationship) between the Case entity and the Portal entity via the admin UI or field manager. When trying to add a link or foreign field, the Portal entity does not appear as a target option. This prevents me from creating a join table like case_portal to replicate the access control logic from KnowledgeBaseArticle.

Could you please clarify:

• Is there a restriction or limitation preventing the Portal entity from being linked to other entities?
• Is there an alternative recommended approach to establish portal-specific filtering for entities like Case?

Thanks!

[yuri]

> Is there a restriction or limitation preventing the Portal entity from being linked to other entities?

It's not possible via the admin UI. It requires manually defining links and a link-multiple field in metadata.