# Preventing Multi-Login Sessions

**URL:** https://community.glideapps.com/t/preventing-multi-login-sessions/75062
**Category:** Ask for Help
**Created:** [July 22, 2024, 10:57am UTC](https://community.glideapps.com/t/preventing-multi-login-sessions/75062 "2024-07-22T10:57:33Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![dezwatz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dezwatz/32/77903_2.png) [@dezwatz](https://community.glideapps.com/u/dezwatz)
#### Post date: [July 22, 2024, 10:57am UTC](https://community.glideapps.com/t/preventing-multi-login-sessions/75062/1 "2024-07-22T10:57:33Z")

</div>

Is there any way to prevent users from simply sharing their login information and creating multiple sessions to access paid content?

For example, Company A is selling a service to track products as it moves through various stages of production. It sells this service on a per user basis to Company B. Company B says they only need one account and (sneakily) shares this account with every employee in their customer service department instead of purchasing in agreement to the T&C they’ve agreed to.

Has anyone else faced this situation? What do I do to prevent it? Thanks!

---

<div class="post-metadata">

### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [July 22, 2024, 1:38pm UTC](https://community.glideapps.com/t/preventing-multi-login-sessions/75062/2 "2024-07-22T13:38:09Z")

</div>

At the moment, there’s no straightforward way to do that. If I have to do this, maybe the only way is associating an email with X lines of device fingerprinting info/IP address.

Every time a user logs in, you check their device fingerprinting/IP address against the list of info you already have from their previous logs in. If they have crossed the allowed number, then you don’t allow them to access content.

---

<div class="post-metadata">

### Author: ![dezwatz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dezwatz/32/77903_2.png) [@dezwatz](https://community.glideapps.com/u/dezwatz)
#### Post date: [July 22, 2024, 1:44pm UTC](https://community.glideapps.com/t/preventing-multi-login-sessions/75062/3 "2024-07-22T13:44:24Z")

</div>

That’s a brilliant solution. Thanks!!

---

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)
#### Post date: [July 29, 2024, 1:44pm UTC](https://community.glideapps.com/t/preventing-multi-login-sessions/75062/4 "2024-07-29T13:44:37Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
