Management UI

README.md

@@ -21,9 +21,31 @@ php artisan serve
 ```
 
 Configure the MySQL connection in `.env` before running migrations. The
-application resolves a business from the request hostname through the
-`business_domains` table. Local development can use a configured local domain
-or the `APP_DEFAULT_BUSINESS_SLUG` fallback.
+application resolves a business only from the request hostname through the
+`business_domains` table; it never guesses a tenant from the first business
+in the database. For local multi-tenant work, map each configured hostname to
+127.0.0.1 in `/etc/hosts`.
+
+## Platform and tenant setup
+
+Migrations create schema only. They do not create a demo business or a
+business owner. After migrating, open `/install` once and create the platform
+administrator. That account can sign in at `/manager/sign-in`, create
+businesses, edit their primary domains, and share the one-time owner setup
+link generated during provisioning.
+
+Business provisioning creates the tenant domain, settings, booking rules,
+opening hours, system roles, owner staff profile, and seven-day owner
+invitation in one transaction. The owner chooses a password through that
+invitation; platform administrators and business owners are separate account
+types.
+
+If demo data is useful for local development, opt into the existing seeder
+explicitly:
+
+```bash
+NEXTCHAIR_SEED_DEMO=true php artisan db:seed
+```
 
 ## Docker deployment
 
@@ -59,6 +81,10 @@ docker compose exec app php artisan key:generate
 docker compose exec app php artisan migrate
 ```
 
+Then visit `http://localhost:8085/install` to create the first platform
+administrator. Do not run migrations or create tenants from container startup;
+the tenant owner is provisioned manually from Manager.
+
 Migrations are intentionally not run by container startup. To inspect the
 application logs: