# View many Ignition SCADA alarms from one UI

**URL:** <https://forum.inductiveautomation.com/t/view-many-ignition-scada-alarms-from-one-ui/113391>\
**Category:** Ignition\
**Created:** [January 19, 2026, 4:39pm UTC](https://forum.inductiveautomation.com/t/view-many-ignition-scada-alarms-from-one-ui/113391 "2026-01-19T16:39:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kris.zawada](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kris.zawada/32/80230_2.png) [@kris.zawada](https://forum.inductiveautomation.com/u/kris.zawada)\
**Post date:** [January 19, 2026, 4:39pm UTC](https://forum.inductiveautomation.com/t/view-many-ignition-scada-alarms-from-one-ui/113391/1 "2026-01-19T16:39:04Z")

</div>

We have several Ignition SCADA servers located at various sites. Alarms are monitored and acknowledged by logging into individual site private networks and loading the Ignition SCADA project using a local URL. From there the alarms are acknowledged. The goal is to have one location to view and acknowledge alarms. Has this problem been solved? Is there a way to do this already?

Is there a reference design that exists for this?

Below is a high-level diagram:

 ![ignition_scada_alarms_bkw](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/5/3541d9f0731d589c55c76a66d773d1e23a11de18.png)

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [January 19, 2026, 5:15pm UTC](https://forum.inductiveautomation.com/t/view-many-ignition-scada-alarms-from-one-ui/113391/2 "2026-01-19T17:15:11Z")

</div>

> [@kris.zawada](#):
>
> Is there a reference design that exists for this?

Within an Ignition [Gateway Network](https://www.docs.inductiveautomation.com/docs/8.1/platform/gateway-network), you should be able to set up a [Remote Tag Provider](https://www.docs.inductiveautomation.com/docs/8.1/platform/tags/tag-providers) for each of the providers where alarms are generated. You can then set up service security to restrict / permit remote access as desired.  
A project running on Physical Location Main or AWS Cloud will then have access view & acknowledge all alarms (matching your desired filter). A user will be able to acknowledge from any project, and that updated alarm state (acknowledgement) will be observed by a user on any other project.