# Enable restricted users to view record specific history

**URL:** <https://forum.manager.io/t/enable-restricted-users-to-view-record-specific-history/59706>\
**Category:** ideas\
**Created:** [January 13, 2025, 8:53pm UTC](https://forum.manager.io/t/enable-restricted-users-to-view-record-specific-history/59706 "2025-01-13T20:53:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ealfardan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/ealfardan/32/63166_2.png) [@Ealfardan](https://forum.manager.io/u/Ealfardan)\
**Post date:** [January 13, 2025, 8:53pm UTC](https://forum.manager.io/t/enable-restricted-users-to-view-record-specific-history/59706/1 "2025-01-13T20:53:33Z")

</div>

As a result of not being able to who made a Purchase Order since those have no Inventory Location fields, we decided to use `Custom Fields` to capture this information so that the receiving staff know that they are receiving the correct order in the correct store.

However, and since users can access other users work, they either used Copy To function to copy orders and this resulted in either no location set or wrong location set in a good percentage of orders.

We are now relying on `History` to tell which user made the order and therefore the location.

This placed a significant strain on the admin staff since they’re now serving as middlemen between those who made the order and those who receive it.

I know some users will be quick to point out that this is a “user error” which is correct, however, I argue that good process design takes WCGs into consideration, not by bullying users to never make a mistake but instead by introducing systematic preventive and corrective controls to address these WCGs.

Although I provided a specific use case for this, however, I believe that the ability to view the `History` of a specific transaction without the ability to Undo should not be an admin only function especially since users are able to view and edit other users work.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [January 13, 2025, 10:45pm UTC](https://forum.manager.io/t/enable-restricted-users-to-view-record-specific-history/59706/2 "2025-01-13T22:45:50Z")

</div>

> [@Ealfardan](#):
>
> however, I believe that the ability to view the `History` of a specific transaction without the ability to Undo should not be an admin only function especially since users are able to view and edit other users work.

So how would you propose this to work? I think that one should be careful to make history open to all kind of users to change as we use it in auditing. Your issue should be resolved in other ways and maybe as you said be part of ensuring users do what they are supposed to do.

---

<div class="post-metadata">

**Author:** ![Ealfardan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/ealfardan/32/63166_2.png) [@Ealfardan](https://forum.manager.io/u/Ealfardan)\
**Post date:** [January 13, 2025, 11:25pm UTC](https://forum.manager.io/t/enable-restricted-users-to-view-record-specific-history/59706/3 "2025-01-13T23:25:27Z")

</div>

> [@eko](#):
>
> So how would you propose this to work?

That’s easy, disable the Undo button like this:

![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/e/7/e7d02c6b3ac1129699a616acf82d50f531f13842.png)