# New login screen

**URL:** <https://community.appfarm.io/t/new-login-screen/1526>\
**Category:** Ask the community\
**Tags:** ui\
**Created:** [November 22, 2024, 9:26am UTC](https://community.appfarm.io/t/new-login-screen/1526 "2024-11-22T09:26:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lars.bergh.hvidsten](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/lars.bergh.hvidsten/32/2486_2.png) [@lars.bergh.hvidsten](https://community.appfarm.io/u/lars.bergh.hvidsten)\
**Post date:** [November 22, 2024, 9:26am UTC](https://community.appfarm.io/t/new-login-screen/1526/1 "2024-11-22T09:26:24Z")

</div>

Hi!

Is it possible to change the theme/ui of the new login screen? We have a custom login app want the UI to be similar to this, or else the user is transferred to a screen that is totally different to our application:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/2/2c51e61526d066b0eef2488adeb4693120e978a4.jpeg)  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/d/dad7ade74bdd34ccc8d62f6448502ad537734834.jpeg)  
We are custom auth with SSO to Azure AD, so when the user is logging in for the first time they are prompted for a pin code to create their user account.

---

<div class="post-metadata">

**Author:** ![kristian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kristian/32/58_2.png) [@kristian](https://community.appfarm.io/u/kristian)\
**Post date:** [November 22, 2024, 9:38am UTC](https://community.appfarm.io/t/new-login-screen/1526/2 "2024-11-22T09:38:43Z")

</div>

Hi!

This second image: Is this when logging in to the App, or Appfarm Create?  
This is how the default login to Apps looks like.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/7/707dc006d25f419f0770f3cda7ee3dc3170398f3.png)

Let’s take a DM on this one

---

<div class="post-metadata">

**Author:** ![lars.bergh.hvidsten](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/lars.bergh.hvidsten/32/2486_2.png) [@lars.bergh.hvidsten](https://community.appfarm.io/u/lars.bergh.hvidsten)\
**Post date:** [November 22, 2024, 9:41am UTC](https://community.appfarm.io/t/new-login-screen/1526/3 "2024-11-22T09:41:56Z")

</div>

Yes from create. Wrong image. Here it is through first time login through sso

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/3/339ac421a0e45292cbe43a515ee40cf46a4c268a.jpeg)

---

<div class="post-metadata">

**Author:** ![kristian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kristian/32/58_2.png) [@kristian](https://community.appfarm.io/u/kristian)\
**Post date:** [November 22, 2024, 10:46am UTC](https://community.appfarm.io/t/new-login-screen/1526/4 "2024-11-22T10:46:18Z")

</div>

Hi!

This one is solved.

The sender email address for pincode-emails when login to Appfarm Create, and the built-in “Confirm email” landing page for new apps users (after auto-creating users via third-party authentication), was changed from [security@appfarm.io](mailto:security@appfarm.io) to [login@appfarm.io](mailto:login@appfarm.io) with this release. This change has already been done a while ago for normal Apps login.

In this case, there is no normal Apps login with Appfarm pincode emails, so this release was the first touchpoint with this change. And with this change, the corporation-specific inbound email filters also needed to be changed. This change should have been communicated by Appfarm prior to the release.

---

<div class="post-metadata">

**Author:** ![kristian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kristian/32/58_2.png) [@kristian](https://community.appfarm.io/u/kristian)\
**Post date:** [November 22, 2024, 7:58pm UTC](https://community.appfarm.io/t/new-login-screen/1526/5 "2024-11-22T19:58:00Z")

</div>

Hi,

A quick update on this one.

A change has been done on our side. The IP of the pin-emails / login-emails from Create were blocked in some cases, but that issue has now been resolved.