# Limit number of sessions using a page

**URL:** <https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [July 28, 2023, 8:35am UTC](https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055 "2023-07-28T08:35:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pablo\_Fernandez\_Expo](https://avatars.discourse-cdn.com/v4/letter/p/c67d28/32.png) [@Pablo\_Fernandez\_Expo](https://forum.inductiveautomation.com/u/Pablo_Fernandez_Expo)\
**Post date:** [July 28, 2023, 8:35am UTC](https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055/1 "2023-07-28T08:35:40Z")

</div>

Hi,

Is there a way to limit the number of sessions that can have a certain page open at the same time?  
I have some pages dedicated to modify tables in SQL and I want to limit the concurrent users as much as possible to avoid parallel modifications.

Maybe looping trough all opened sessions and checking if there is "space" for the specific page to be opened and if not just redirect the page to a "waiting page" with a message "Max number of sessions. Please wait until another user closes the page" and a refresh button to re-run the action.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [July 28, 2023, 9:09am UTC](https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055/2 "2023-07-28T09:09:36Z")

</div>

That's not how the web works. I think there is something wrong with your strategy and you need to use a record lock or similar when the first user starts to edit.

---

<div class="post-metadata">

**Author:** ![DNice](https://avatars.discourse-cdn.com/v4/letter/d/858c86/32.png) [@DNice](https://forum.inductiveautomation.com/u/DNice)\
**Post date:** [July 28, 2023, 10:52am UTC](https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055/3 "2023-07-28T10:52:34Z")

</div>

You are right in being weary of this kind of power to "modify tables" from a web app. I would suggest you add audit log tracking to capture all changes users are making.

In the past a solution that worked for me in this situation is to have a "[pageName]/login" tag for that specific page. I put a login/logout button on that page that writes/erases your userID to that "pageName]/login" tag. Users can only make changes to that data if your userID matches that tag value.

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [July 28, 2023, 12:21pm UTC](https://forum.inductiveautomation.com/t/limit-number-of-sessions-using-a-page/77055/4 "2023-07-28T12:21:15Z")

</div>

I had to do something similar a while back. Instead of locking things down. I alerted via popup if two or more users were editing at the same time. I did this with messages.