Next step · What to do next

Add customer accounts and sign-in

What you may see

I want customers to log in and see their orders

Why this step

Accounts add trust and repeat orders, but also risk; use a proven sign-in service, never write password handling yourself.

Before you start

Do customers really need accounts, or is guest checkout enough?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Add customer accounts and sign-in

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Accounts add trust and repeat orders, but also risk; use a proven sign-in service, never write password handling yourself.

DO THESE STEPS, IN THIS ORDER
1. Choose with me the sign-in methods (email and password, link by email, Google) and explain each in plain words with its trade-offs.
2. Build sign-up, sign-in, sign-out and password reset pages in English and Arabic using the sign-in service, with clear errors and rate limits, and cookies that are secure and lax.
3. Protect pages and data on the SERVER by user and role; add database rules so each user sees only their own records.
4. Add the live and local addresses to the service's allowed redirect list and test on iPhone Safari too.
5. Test with two test users trying to read each other's data.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Sign-up, sign-in, reset and sign-out work on the live site and on phones, and users cannot see each other's data.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not store passwords yourself or invent your own encryption.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Choose with me the sign-in methods (email and password, link by email, Google) and explain each in plain words with its trade-offs.
Build sign-up, sign-in, sign-out and password reset pages in English and Arabic using the sign-in service, with clear errors and rate limits, and cookies that are secure and lax.
Protect pages and data on the SERVER by user and role; add database rules so each user sees only their own records.
Add the live and local addresses to the service's allowed redirect list and test on iPhone Safari too.
Test with two test users trying to read each other's data.

Do not do this

Do not rely on hidden buttons for protection.
Do not store passwords yourself or invent your own encryption.

Try another entry