# Login for @domain.com

**URL:** <https://community.glideapps.com/t/login-for-domain-com/43128>\
**Category:** Ask for Help\
**Created:** [June 16, 2022, 1:19am UTC](https://community.glideapps.com/t/login-for-domain-com/43128 "2022-06-16T01:19:09Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 16, 2022, 1:19am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/1 "2022-06-16T01:19:10Z")

</div>

Hello there!

I’d like to configure the login logic for my app as follows:

- anyone in with an email address in my domain can log in and view the app content
- anyone else cannot log in

Is there a canonical way to achieve this?

(Keywords: authorization, authentication, domain)

---

<div class="post-metadata">

**Author:** ![eltintero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eltintero/32/76520_2.png) [@eltintero](https://community.glideapps.com/u/eltintero)\
**Post date:** [June 16, 2022, 3:53am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/2 "2022-06-16T03:53:38Z")

</div>

I’m 99% sure you can have [domain.com](http://domain.com) in the email column of your user profiles table, and you’ll whitelist the whole domain… @Ian can confirm this.

---

<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:** [June 16, 2022, 3:56am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/3 "2022-06-16T03:56:13Z")

</div>

Yeah, the last time I tested that it worked as you describe.  
Obviously needs to be a private app.

---

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 16, 2022, 11:05pm UTC](https://community.glideapps.com/t/login-for-domain-com/43128/4 "2022-06-16T23:05:16Z")

</div>

This doesn’t work for me, but where I’m stuck may be something unrelated:

I don’t think I have the `User Profile` set up correctly. I am not trying to do anything special, just get something default working. The prompt suggests “Please assign a user image column,” but the dropdown is grayed out. The `User Profile` shows a `Lock` icon in the left nav, which may be relevant - I don’t know the intended meaning there. Maybe that’s normal?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/f/ef39bd57e3599b25cec5288a735b02c61527b461.png)

---

<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:** [June 17, 2022, 12:03am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/5 "2022-06-17T00:03:13Z")

</div>

Do you have an “Image” type column in your Users table?

---

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 17, 2022, 2:18am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/6 "2022-06-17T02:18:52Z")

</div>

Yes, I’ve tried with a few column types.

Airtable has an ‘attachments’ column type which it uses for images. (In other contexts, Glide correctly recognizes this as containing images.) So maybe that is related to the issue. I’ve tried that, and URL type, and lastly defining the column as image from the Glide UI (but it’s still an Airtable column).

---

<div class="post-metadata">

**Author:** ![SantiagoPerez](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/santiagoperez/32/16807_2.png) [@SantiagoPerez](https://community.glideapps.com/u/SantiagoPerez)\
**Post date:** [June 17, 2022, 6:23pm UTC](https://community.glideapps.com/t/login-for-domain-com/43128/7 "2022-06-17T18:23:04Z")

</div>

Hi @adam1,

Could you submit a support ticket so we can take a closer look?

Please, add a support link and a video of the issue.

[https://glide-help.zendesk.com/hc/en-us/requests/new](https://glide-help.zendesk.com/hc/en-us/requests/new)

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [June 17, 2022, 6:51pm UTC](https://community.glideapps.com/t/login-for-domain-com/43128/8 "2022-06-17T18:51:55Z")

</div>

> [@adam1](#):
>
> anyone in with an email address in my domain

Did you also try ‘@domain.com’ as opposed to just ‘[domain.com](http://domain.com)’?

---

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 17, 2022, 10:42pm UTC](https://community.glideapps.com/t/login-for-domain-com/43128/9 "2022-06-17T22:42:52Z")

</div>

> [@SantiagoPerez](#):
>
> Hi @adam1,
> 
> Could you submit a support ticket so we can take a closer look?
> 
> Please, add a support link and a video of the issue.
> 
> [https://glide-help.zendesk.com/hc/en-us/requests/new](https://glide-help.zendesk.com/hc/en-us/requests/new)

Done this, thanks!

---

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 23, 2022, 7:03pm UTC](https://community.glideapps.com/t/login-for-domain-com/43128/10 "2022-06-23T19:03:41Z")

</div>

Update: this worked after disabling “Allow image update.”

---

<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:** [June 24, 2022, 12:34am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/11 "2022-06-24T00:34:06Z")

</div>

That’s weird. Not sure how that relates to a whitelist set up.

---

<div class="post-metadata">

**Author:** ![adam1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam1/32/43879_2.png) [@adam1](https://community.glideapps.com/u/adam1)\
**Post date:** [June 24, 2022, 2:04am UTC](https://community.glideapps.com/t/login-for-domain-com/43128/12 "2022-06-24T02:04:49Z")

</div>

I agree, it was quite counterintuitive. I hadn’t thought they were connected.

My theory, although I haven’t tested this: perhaps the ‘allow image update’ filtered for writable image columns. My Airtable API key grants read-only access at this time, so no columns satisfied the filter.
