# Check if alarm settings changed

**URL:** <https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718>\
**Category:** Ignition\
**Tags:** ignition78\
**Created:** [February 20, 2019, 5:02pm UTC](https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718 "2019-02-20T17:02:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aykchoe](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@aykchoe](https://forum.inductiveautomation.com/u/aykchoe)\
**Post date:** [February 20, 2019, 5:02pm UTC](https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718/1 "2019-02-20T17:02:25Z")

</div>

We are trying to have better control of alarms, and one step is to prevent/track changes to these settings.  
What are some ways to accomplish this?

Is there a way to have permissions inside of designer to allow changes to certain aspects, like alarming?

Is there a way to track changes to alarming done in designer through event logging?

---

<div class="post-metadata">

**Author:** ![mrogers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mrogers/32/4110_2.png) [@mrogers](https://forum.inductiveautomation.com/u/mrogers)\
**Post date:** [February 20, 2019, 5:18pm UTC](https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718/2 "2019-02-20T17:18:29Z")

</div>

I don’t think there’s a way to do this normally, unfortunately. However, something we do is have a folder of config memory tags, for things like priority, set point, etc. and have the alarm properties bound to those. That way, the memory tags are easier to monitor.

---

<div class="post-metadata">

**Author:** ![aykchoe](https://avatars.discourse-cdn.com/v4/letter/a/71c47a/32.png) [@aykchoe](https://forum.inductiveautomation.com/u/aykchoe)\
**Post date:** [February 20, 2019, 5:33pm UTC](https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718/3 "2019-02-20T17:33:09Z")

</div>

Could you explain how having alarm properties bound to memory tags would make it easier to monitor?

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [February 20, 2019, 5:49pm UTC](https://forum.inductiveautomation.com/t/check-if-alarm-settings-changed/22718/4 "2019-02-20T17:49:44Z")

</div>

I’m guessing he has historian or a transaction group enabled on those memory tags in order to track any changes.

I don’t believe there is a permission or anything that will prevent changes to specifically just alarms. You could make a separate user group though and have that group only have access to add/remove/modify tags through client permissions or through the tag provider settings. I haven’t really used either of these before, so I’m not sure which would be preferred or if there are any further quirks.

Tag Provider: [https://docs.inductiveautomation.com/display/DOC79/Tag+Provider+Security](https://docs.inductiveautomation.com/display/DOC79/Tag+Provider+Security)  
Client Permissions: [https://docs.inductiveautomation.com/display/DOC79/Project+Properties#ProjectProperties-ClientPermissions](https://docs.inductiveautomation.com/display/DOC79/Project+Properties#ProjectProperties-ClientPermissions)