BUG: "Email not authorized" when using Allowed Email Domains (Explorer Plan)

Hi everyone,

I am building a student exchange platform for my university on the Explorer plan, and I am running into a critical sign-in issue.

My setup in Settings > Access:

  • “Users in the users table” is UNCHECKED.

  • “My Team team” is UNCHECKED.

  • “Allowed email domains” is CHECKED with two domains added: @uni-university.de and @mail.uni-university.de

  • I am using PIN emails for authentication.

My setup in Settings > User Data:

  • “Collect real user email addresses” is CHECKED.

  • The User Profile screen is correctly mapped to my “Users” table, with the Email column properly assigned.

  • Row Owners is NOT enabled on the email column.

The issue: When testing the published app via the live URL/QR Code with a valid @mail.uni-paderborn.de email address, Glide blocks the sign-in with the error message stating the email is not authorized to access the app. I have re-typed the domains to ensure there are no hidden spaces, but it still rejects valid emails.
Currently, the only way to access the application is for me to personally send an invitation to the email address so that access can be granted.
Since the goal is for any student from the university to auto-generate a row in the Users table upon their first sign-in, how can I bypass this error? Is there a known bug with domain whitelisting not recognizing newly inputted emails, or is there a step I am missing?

Thanks in advance for your help!

The email you tried doesn’t match what you indicate that you entered as allowed domains.

Are you trying to allow two domains at the same time, or did you try one at a time?

Also, the @ symbol is not required.

In addition to what Jeff noted, email addresses in that domain do not qualify as personal users, which is all that the Explorer plan allows. But given it is an educational domain, I expect that Glide will allow it if you ask. You can do that via Personal User Validator Agent

Thank you so much for your reply! You were completely right. I made a typo when writing it out, but they were indeed the same email addresses. The real issue was actually the ‘@’ symbol—removing it fixed the problem immediately. Thanks again for your help!