Create a feature to duplicate cards from a pipe to another one based on criterias

How would this differ from using reports for export and the import app for import (duplication)into the other pipe?

I’m sorry maybe I couldn’t explain right.

This feature must be permit the update for each card based on changes or at least by automation to make sure that customers can see all their cards updated and interact with them.

Doesn’t make sense create a tool to handle a flow and don’t use automation for control, update and other routines.

The main question here is: Request Tracker is based on link and suppose that an user send the link to another person, or maybe the e-mail is hacked anyone can see the cards and this is a huge privacy and cybersecurity breach.

My customers and the DPO is very concerned about the this could be create a situation handled by LGPD.

Hey @fernando-scarduelli and @Rodrigo Leite, look at this post. It relates a lot to what we were discussing yesterday, it touches both people following things inside Pipefy and how this permissions work. cc @maurivan. 

Thanks @Ezequiel Souza for this feedback, it will be useful for our next plans of improvement on Pipefy!  

@Ezequiel Souza I have a similar case and I keep all cards in the same PIPE, but I leave users with limited vision for the cards they are responsible for.

Another solution I developed to solve a similar problem is a form where the customer fills in the process ID and receives in the email (previously authorized) the updated status of the process (card).

Hi Lucas.

This solution that you proposed is very fragile, because the automation, sometimes, there is delay and while this happens all cards without correct assignees can be viewed by others, In my case, I have external customers that never can see others cards from other customers.

So my suggestion is to avoid this kind of situation.