# Moving the sign-in page

> Moving the sign-in page takes about twenty minutes, and nobody can sign in while it runs or until your record has spread. People already signed in stay signed in. Do it out of hours — and Use the Sapilon sign-in address puts it back in one click.

Source: https://sapilon.com/docs/project/sign-in-address
Last updated: 2026-09-18

---

When someone signs in to your app, they are sent briefly to a sign-in page and then back again.
That page lives at a Sapilon address — something like `auth.your-project.sapilon.com` — and most
people never notice it.

If you would rather they saw your own name there, you can move it to an address like
`login.example.com`. This is a bigger step than [adding a web address](./web-address.md), and it
is worth understanding why before you start.

## Read this part first

**The move takes about twenty minutes, and nobody can sign in for any of it.** Sign-in works by a
service holding exactly one address, so moving it means taking the old one down and building the
new one. There is no overlap and no way to make it shorter.

**And it stays down after that** — until the record you add has spread across the internet. That
is usually minutes, but it is not instant.

**People already signed in stay signed in.** They are not logged out and they lose nothing. What
stops working is _starting_ a new sign-in: new visitors, and anyone whose session has run out.

So: **do this out of hours.** A quiet evening, a weekend morning — whenever the fewest people are
trying to get in. Everything else about your app keeps working normally throughout; only signing
in is affected.

## What has to be true before you start

**It has to be a name under your domain, not the whole domain.** `login.example.com` works;
`example.com` does not. The sign-in service will not accept a whole domain, so Sapilon refuses it
before you spend any time on it.

**Your domain has to already point somewhere.** The sign-in service checks that `example.com`
itself resolves to a real address before it will host a page under it. If your domain does not
point anywhere yet — you bought it and never used it — point it at your website first. Sapilon
checks this up front and tells you if it is missing, rather than letting you find out twenty
minutes in.

## How it goes

1. On **Go Live → Publish**, in the **Web addresses** card, choose **Change the sign-in address**.
2. Type the address, like `login.example.com`.
3. Add the verification record it gives you, exactly as written, and wait for it to show as
   secured. **Nothing has moved yet** — sign-in is still working normally, and you can stop here
   and come back another day.
4. When you are ready, choose **Move the sign-in page** and confirm. This is the point of no
   return for the next twenty minutes.
5. Watch the progress. The page tells you which step it is on.
6. When it finishes, add the last record it gives you. Sign-in comes back as that record spreads.

## If something goes wrong

**Use the Sapilon sign-in address** puts everything back the way it was. It is on the same page,
always, whatever state your address is in — including after a failure, and including while a move
is still running. You never need to ask anyone or wait for support.

It takes about as long as the move did, because it is the same operation in reverse. But it needs
nothing from you: the address it goes back to is one Sapilon has always owned and always kept
working.

## Afterwards

Your sign-in page is at your address, with your name on it. The Sapilon sign-in address stops
answering — unlike your app's web address, this one really does move rather than being added
alongside, because sign-in can only live in one place.

If you later remove the address or change your mind, use the same button. Nothing about your
users' accounts, passwords, or sessions depends on which address the page lives at.