# How to make it so operators can only shelve alarms once? **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [September 17, 2024, 12:39pm UTC](https://forum.inductiveautomation.com/t/how-to-make-it-so-operators-can-only-shelve-alarms-once/96058 "2024-09-17T12:39:25Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![aspatchek2013](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aspatchek2013/32/85339_2.png) [@aspatchek2013](https://forum.inductiveautomation.com/u/aspatchek2013)\ **Post date:** [September 17, 2024, 4:14pm UTC](https://forum.inductiveautomation.com/t/how-to-make-it-so-operators-can-only-shelve-alarms-once/96058/2 "2024-09-17T16:14:26Z")
The Alarm Status table is a great starting point for many (most) use cases. However, there is a limit to the customization that can be added to it. You might be at a point where building your own Alarm Status table would be preferred. You can [query the alarms](https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-alarm/system-alarm-queryStatus), handle each alarm as a [PyAlarmEvent](https://docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/scripting-object-reference#pyalarmevent) object, and ultimately display all of these in a standard table component. Doing so provides much more control over specific needs - like [scripting your own shelving](https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-alarm/system-alarm-shelve). Or the middle ground here might simply be to use the built-in Alarm Status table, but disable the ability to shelve/unshelve alarms from the table itself. Then add your own shelving button elsewhere that allows you to script your own shelving with your custom needs. --- _[View the full topic](https://forum.inductiveautomation.com/t/how-to-make-it-so-operators-can-only-shelve-alarms-once/96058)._