Securing PegaSocial Documents based on access roles
Hi,
We are trying to incorporate security for the documents attached to a case ( Which are instances of PegaSocial-Document instances ) .
For the general documents which are not the instances of PegaSocial-Document , we have attachment category option in which security can be incorporated but where as for PegaSocial-Document instances , as the attachment category is "pxDocument" ( Final rule ) , we are not able to add additional security . Is there a preferred way to add the security for these ?
Updated: 22 Jul 2024 3:24 EDT
Pegasystems Inc.
GB
@vamseekk does the explanation in a past question https://support.pega.com/question/how-can-documents-pinned-pegasocial-space-be-referenced help? Also see @ohart reply in Document Attachment Handling
In Pega Platform, you can control access to attachments in a Case by applying security policies to Case content. This ensures that users only interact with attachments that are appropriate for their role in a business process. You secure Case attachments by first categorizing attachments and then defining what actions users can perform on each category. However, for PegaSocial-Document instances, the attachment category is "pxDocument", which is a final rule, and you cannot modify it directly. If you need to add additional security, you may need to create a custom solution, such as creating a new attachment category and using it for your PegaSocial-Document instances. Please note that any custom solution should be carefully designed and tested to ensure it meets your security requirements.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
@vamseekk does the explanation in a past question https://support.pega.com/question/how-can-documents-pinned-pegasocial-space-be-referenced help? Also see @ohart reply in Document Attachment Handling
In Pega Platform, you can control access to attachments in a Case by applying security policies to Case content. This ensures that users only interact with attachments that are appropriate for their role in a business process. You secure Case attachments by first categorizing attachments and then defining what actions users can perform on each category. However, for PegaSocial-Document instances, the attachment category is "pxDocument", which is a final rule, and you cannot modify it directly. If you need to add additional security, you may need to create a custom solution, such as creating a new attachment category and using it for your PegaSocial-Document instances. Please note that any custom solution should be carefully designed and tested to ensure it meets your security requirements.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Controlling access to Case attachments
Considerations for ingesting documents, extracting data, and populating cases > A
Security Checklist when deploying on Pega Cloud > Secure file uploads
DCS
AU
@MarijeSchillern , our use case is restricting some set of operations ( Such as ability to view certain documents , operations such as adding new attachments / delete certain documents ) based on the user access role . It seems the links you have provided does not cover that aspect . Is there any OOTB way to address this requirement ?
Updated: 23 Jul 2024 6:43 EDT
Pegasystems Inc.
IN
What release of Pega are you on? Is this traditional UI application or constellation?Are you adding Documents as an attachment to a case via Files & document widget?
In constellation portal we do not support wrapping attachment via PegaSocial-Document.
We do not have OOTB capability to add category to PegaSocial-Document.
Hope this is helpful.
DCS
AU
@Rekha Rani,we are using pega infinity 23.1 with traditional UI ( ThemeCosmos ) & attaching the documents using OOTB case attachments widget which is creating PegaSocial-Document instances in the backend . Our requirement is to hide certain sensitive documents based on the current user role & trying to understand if it is feasible by Pega Social documents OOTB or do we need to implement our custom solution .