Guide

Add a login to your app

Members, staff and an owner. Different people see different screens.

Company single sign-on is in the code but no identity provider is connected yet, so it is not something you can switch on today.

What you need first

Work out who logs in and what each of them is allowed to do.

  • Who logs in — customers, staff, or both.
  • Which screens must be hidden from people who are not logged in.
  • For Google or GitHub sign-in, your own keys from those services.

01 · Ask for accounts

“Let customers sign up and log in with an email and password.” Passwords are between 8 and 128 characters. Sessions are handled on the server, not left lying around in the browser.

02 · Decide the roles

Six roles are available, and an app usually uses two or three of them.

  • Customer — buys, books, sends enquiries
  • Member — a signed-up regular
  • Staff — handles the day-to-day work
  • Author — writes the content
  • Admin — manages people and settings
  • Owner — everything, including deletion

03 · Protect the screens

Say it plainly: “only staff and above can open the bookings list”. The check has to hold in two places — on the screen and at the data boundary. Asking for both is what stops someone reaching the data by typing the address directly.

04 · Add Google or GitHub sign-in if you want it

These use your own keys, entered per project. They are not our platform keys, which means the accounts belong to you and nothing is shared with other projects. Paste them into the project secrets screen.

05 · Test it logged out

Open the protected page in a private window. You should be sent to the login screen. Then log in as each role you created and check that each sees only what it should.

You are done whenA logged-out visitor is turned away from the protected page, and each role sees exactly its own screens.

If you get stuck

I forgot the owner password. Ask for a password reset flow in the app, or create a new owner account from the code editor. Do not leave the reset route open to the public afterwards.

Can I use Kakao or Naver login? Not as a built-in option today. Email and password work now, and Google and GitHub work with your own keys.

The pre-publish check says authentication is unresolved. That means a protected route still has an unfinished marker on it. Ask the AI to finish it, then run the check again. It stays blocked until the check itself passes.

Read next

Check it before publishing

Nine checks, and what each one looks at.

The pre-publish scan

Why publishing stays blocked until it passes.

Template gallery

Dashboards and member areas come with logins.

Something here not working? Check the FAQ first — then write to us and we will answer.