Adding login to your site

Many sites need accounts — members areas, dashboards, saved orders. You do not configure an auth system by hand: you describe what you want, and the agent builds real sign-up and login into your site.

Asking for accounts

1. Tell the agent what accounts are for: "visitors can create an account and save their bookings."
2. Say how people should sign in — email and password is the default; social sign-in can be added where your backend supports it.
3. Say what is protected: "the dashboard is only visible after login."

The agent creates the sign-up and login screens, the user store behind them, session handling, and the rules that keep protected pages closed to signed-out visitors. Passwords are handled by the backend's auth system — they are never stored as readable text.

Managing your site's users

• Ask the agent "how many users signed up this week?" — it can query the user store and report back.
• Admin views are just pages: ask for "an admin page only I can open that lists signups."
• Password reset and email confirmation flows are part of the build — ask if you want them styled differently.

Your site's users are not Black Whole users

Your Black Whole account is how you sign in to build. Your site's users are accounts inside your project, stored in your project's backend, and they exist only there. Someone signing up on your site gets no access to your workspace, and deleting your site's test users never touches your Black Whole account.