👤 For process owners and pipe admins
🔐 These practices apply to all plans. Feature access depends on your plan and account permissions.
🎯 For deciding who can act, investigating changes, and recovering cards
A reimbursement request disappears from the board just as the team is about to verify the payment. The team needs to find out whether the card moved to another phase or was deleted. If a process rule also changed, editing it before checking what happened could affect requests that are still in progress.
By the end, you’ll know how to review access to a pipe, where to look when something changes, and when you can recover a card from Trash.
In the Processos sob controle training, João Pedro Castro used a reimbursement pipe to show how teams can prevent issues, investigate them, and recover cards.
Keep learning with Pipefy training
Join upcoming sessions and bring your questions to our specialists. Explore the training page in Portuguese.
What you will learn:
Decide who can view, work in, and manage a pipe
Start with what each person needs to do. Someone requesting reimbursement needs to submit the request and follow its progress. The people processing reimbursements may need to edit and move cards. Whoever maintains the pipe needs to understand its rules before changing fields, phases, or automations.
Review access at two levels. The company role determines access across the account. The pipe role determines what someone can do within that process. A company member can also be an admin of their team’s pipe. If someone has admin access at the company level, include that wider access in your review. See company roles and permissions. If the process handles confidential data, also review pipe visibility and who has access.
Give requesters a way to check progress
In the demo, a reimbursement Interface showed requests created by the person viewing them and displayed selected columns. When using this approach, choose who can open the Interface and test what two different people can see, including when they open request details. See how to filter and share Interfaces.
Look in the right activity record
If you can still open the card, its activity timeline helps you reconstruct what happened. In the rejected reimbursement from the demo, the timeline showed that an AI Agent updated the triage information and then moved the card. Use that sequence to find the action behind the outcome and check which rule applied.
If the card has disappeared, check the Card activity tab in the pipe’s Activities for a deletion or move. If a field disappeared or a rule changed, ask a pipe admin to check Configuration changes. The pipe’s activity records show what happened, who performed the action, and when.
Check what can be recovered
In the demo, a reimbursement card came back to the board from Trash. A pipe admin can restore a card sent to Trash within 15 days if its original phase still exists. Note which card you’re recovering and check its phase and information once it’s back. See when a card can be restored from Trash.
For changes to the pipe itself, check what else could be affected. Before removing a field that explains the decision to the requester, check whether a message, a conditional rule, or another part of the process uses it. Review the guide to the Flow view in Portuguese to locate phases, fields, and automations, and use the Map to check connections, such as the link between the reimbursement pipe and the employee database.
Questions answered in the training
My pipe has 40 admins. How can I reduce the risk?
Give admin access to the people who maintain the pipe and understand its rules. For people who process requests, check whether the pipe member role meets their needs. Use a viewing role for people who need to consult cards, or restricted view for people who only work on cards they created or were assigned. Schedule a recurring access review and check again when someone changes roles. If the team needs to move cards and deletion should be reserved for admins, use the control for who can delete cards.
How can I let only managers approve purchases over R$10,000?
Keep the approval in the same pipe if the request follows the same overall process. Use the purchase amount to route requests over the limit to a manager, and give analysts a way to track progress. Test both roles: the manager should be able to record the decision, and the analyst should be able to see the status without access to the approval action. Assignment routes the work. Permissions and the channel people use determine which actions they can take. See how to route approvals by purchase amount.
How do I bring customer onboarding across five teams into a pipe?
Walk through a real onboarding request and mark when each team receives the work and when it can hand it over. Use those handovers to define your phases. Use fields for the information each phase needs to collect and automations for handovers that follow a clear rule. For each phase, agree on an owner, what must be complete before moving on, a time limit, and what to do when work is overdue. See how phase deadlines work.
Test access with a sample request
Pick a pipe and follow a sample request as a requester, an operator, and an admin. Note what each person can see and do. Compare that with their responsibilities and fix the first mismatch you find.
Before moving on, confirm that you understand:
☐ Who can track requests, work on them, and manage the process.
☐ Where to review card activity and where to investigate pipe changes.
☐ When a pipe admin can restore a card from Trash.
To practice handovers between teams, watch the walkthrough on building phases with owners and exit criteria in Portuguese on Pipefy Academy.


