# Multiple clients editing/viewing same form/database

**URL:** <https://forum.inductiveautomation.com/t/multiple-clients-editing-viewing-same-form-database/57335>\
**Category:** Ignition\
**Tags:** ignition81, scripting, vision\
**Created:** [March 17, 2022, 9:51pm UTC](https://forum.inductiveautomation.com/t/multiple-clients-editing-viewing-same-form-database/57335 "2022-03-17T21:51:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![josborn](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@josborn](https://forum.inductiveautomation.com/u/josborn)\
**Post date:** [March 18, 2022, 1:02am UTC](https://forum.inductiveautomation.com/t/multiple-clients-editing-viewing-same-form-database/57335/2 "2022-03-18T01:02:10Z")

</div>

The link you shared has some good info.

> [@Multiple users/clients editing/viewing single databse](https://forum.inductiveautomation.com/t/multiple-users-clients-editing-viewing-single-databse/38473/10):
>
> I’ve never done that. Certainly need something in the gateway to moderate access. Will be a nightmare to manage broken connections or sudden client shutdown. I strongly recommend against a window lockout approach.

From the post it sounds like notifications are preferable to a hard lockout, though i could envision scenarios where you employ lockout, like if bad data resulted in a hazardous condition.

---

_[View the full topic](https://forum.inductiveautomation.com/t/multiple-clients-editing-viewing-same-form-database/57335)._
