# Using Perspective for approvals/dispositions

**URL:** <https://forum.inductiveautomation.com/t/using-perspective-for-approvals-dispositions/85655>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [February 13, 2024, 7:14pm UTC](https://forum.inductiveautomation.com/t/using-perspective-for-approvals-dispositions/85655 "2024-02-13T19:14:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\
**Post date:** [February 13, 2024, 7:14pm UTC](https://forum.inductiveautomation.com/t/using-perspective-for-approvals-dispositions/85655/1 "2024-02-13T19:14:33Z")

</div>

Looking for some examples and best practices.

I'd like to use Perspective to track off-quality product, manage the approval/disposition flow and keep traceability of the actions.

This is what I was thinking:

1. A project that a user could flag product for hold/disposition.
2. Leverage the alarming and email modules to give notifications to users (quality managers) that don't currently have the project open.
3. Add blob storage to the DB or possibly link a fileserver so a user could capture pictures to attach to the non-conformance.

Has anyone done anything similar? What worked best for you?

Thanks!