PRACTICAL ROUTE Use a ready sign-in project to keep a practice note private and test both allowed and denied access. Your role: Choose only fictional test content and verify who can actually obtain it. 1. Use the supplied project and ask your coding assistant to carry out the implementation. You do not need to write HTML, JavaScript or SQL yourself. 2. Follow the current lesson steps, configure only your own permitted accounts and check the result in the actual page/provider. 3. Keep expected results and observed results separate. Record the exact blocked step if you cannot run a live check. The detailed setup below is available to you and your assistant. Code explanations and extra implementation exercises are optional; important access/privacy checks are still part of the practical lesson. --- REQUIRED SETUP (CODE READING IS OPTIONAL) --- Use a separate Supabase practice project. Configure its Email authentication and a permitted test recipient/custom SMTP. In the Magic Link email template, include {{ .Token }} so the message contains an OTP code rather than only a link. Put only the project URL and PUBLISHABLE key in public/config.js. Never use a secret/service-role key there. Serve public/ over localhost HTTP or your own HTTPS host; module imports do not work reliably from file://. Test only inboxes you control. Sender/account limits may require provider configuration. This is a separate practice project. public/ is the website folder; netlify/functions/ contains server-only functions. Install Node and Netlify CLI for local function testing, or deploy this project to your own Netlify account. Put real credentials in server environment variables, never in public/ or Git. No provider request runs just by opening these files. Account steps and real delivery must be checked in your own account. Set SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY and PRIVATE_NOTE in the server environment. The private note is not in public/ or repository source. The server verifies the incoming user token with the authentication service; it does not trust the browser’s local account object. For exact local commands and private environment names, read run-locally.txt and server-env.example.txt.