# Knowing who tripped an alarm **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective, scripting\ **Created:** [July 18, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528 "2023-07-18T16:13:49Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 18, 2023, 6:06pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/5 "2023-07-18T18:06:25Z")
> [@Cameron\_Nickle](#): > > and not have to go through the tagging system Alarming is fundamentally tied to tags, not client sessions. Which is why the auditing system is so useful when backtracking from alarms to potential user causes. Perhaps you should make a feature request, with specific details on how you would like it to work. Related: > [@Alarming in perspective via no tag or client tag or some other alertanive](https://forum.inductiveautomation.com/t/alarming-in-perspective-via-no-tag-or-client-tag-or-some-other-alertanive/75796): > > Hi all, I'm working on triggering my alarm pipeline from my perspective session. I've designed everything to be done through the session properties so each user has their own values of interest. The problem I am now facing is I have no tags, so I want to know if there is a way to set-off an alarm pipeline without a tag. (From what I've been reading this seem unlikely but I thought I'd ask) The more likely option is I will need a client tag to do this. I am wondering how I go about making a cli… --- _[View the full topic](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528)._