# Security - by domain

**URL:** https://community.glideapps.com/t/security-by-domain/65317
**Category:** Ask for Help
**Created:** [August 23, 2023, 9:10pm UTC](https://community.glideapps.com/t/security-by-domain/65317 "2023-08-23T21:10:45Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)
#### Post date: [August 23, 2023, 9:10pm UTC](https://community.glideapps.com/t/security-by-domain/65317/1 "2023-08-23T21:10:45Z")

</div>

I thought I had set up security by domain but it didn’t seem to work. I shared a link with some uses, but they reported they did not receive a pin and could not access the application.

Can someone please confirm:

(1) I select private for the user sign-in Settings, and

(2) what entry should I use for the domain field? for example, if my company uses email addresses [John.doe@abc.com](mailto:John.doe@abc.com) then do I simply specify [abc.com](http://abc.com) into the domain field?

(3) I assume I do not then need to add any email addresses for potential future users (that work at [abc.com](http://abc.com)) into the users table?

For info after trying this, and it not working, I reverted back to manually adding names into the users table, and this worked OK. However, I would be really happy to use the domain approach.

---

<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: [August 23, 2023, 11:25pm UTC](https://community.glideapps.com/t/security-by-domain/65317/2 "2023-08-23T23:25:13Z")

</div>

Can you try @abc.com instead of just [abc.com](http://abc.com)

---

<div class="post-metadata">

### Author: ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)
#### Post date: [August 24, 2023, 7:26am UTC](https://community.glideapps.com/t/security-by-domain/65317/3 "2023-08-24T07:26:13Z")

</div>

Yes I will try that. Thank you.

---

<div class="post-metadata">

### Author: ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)
#### Post date: [August 24, 2023, 10:22am UTC](https://community.glideapps.com/t/security-by-domain/65317/4 "2023-08-24T10:22:44Z")

</div>

Ok it turns out you just need [abc.com](http://abc.com). Not @abc.com - my colleagues had missed the PIN. But it works now.

I do think such an example should be inserted into the Glide documentation 🙂

---

<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: [August 24, 2023, 11:39pm UTC](https://community.glideapps.com/t/security-by-domain/65317/5 "2023-08-24T23:39:45Z")

</div>

@Darren_Murphy I think we can consider adding an example for this in the docs.

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [August 25, 2023, 2:57pm UTC](https://community.glideapps.com/t/security-by-domain/65317/6 "2023-08-25T14:57:05Z")

</div>

Yes, agreed. Will follow up.

---

<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: [September 1, 2023, 2:57pm UTC](https://community.glideapps.com/t/security-by-domain/65317/7 "2023-09-01T14:57:18Z")

</div>

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