Added admin mode, read only status for inactive accounts, and resuce verification

README.md

@@ -7,9 +7,9 @@ FlockPal is a Dockerized TypeScript app for tracking flock health with a clean,
 - Passwordless authentication only
 - Magic-link email sign-in
 - OAuth-ready login flow for Google, Microsoft, and Apple
-- Multi-workspace model with `standard` household and `rescue` modes
-- Shared workspace member management for both households and rescues
-- Separate per-workspace billing plan foundation with `rescue_free`, `household_basic`, `household_plus`, and `household_macaw`
+- Multi-flock model with `standard` household and `rescue` modes
+- Shared flock member management for both households and rescues
+- Separate per-flock billing plan foundation with `rescue_free`, `household_basic`, `household_plus`, and `household_macaw`
 - Bird profiles with name, tag ID, and species
 - Bird DOB and gotcha day fields
 - Daily weight recordings
@@ -22,10 +22,10 @@ FlockPal is a Dockerized TypeScript app for tracking flock health with a clean,
 ## Planned next steps
 
 - Medication and care reminders
-- Invitation acceptance and onboarding polish for workspace members
+- Invitation acceptance and onboarding polish for flock members
 - Stripe or equivalent billing integration for paid household tiers
 - Scheduled reminder delivery for birthdays, gotcha days, and care events
-- Audit logging for workspace access changes and bird transfers
+- Audit logging for flock access changes and bird transfers
 
 ## Development
 
@@ -59,13 +59,13 @@ docker compose -f docker-compose.prod.yml up --build -d
 3. The production backend runs the compiled Node app from `dist/app.js`.
 4. The production frontend is built with Vite and served by Nginx on port `3000`.
 
-## Auth and workspace notes
+## Auth and flock notes
 
-- One user can belong to multiple workspaces.
-- A rescue member can also keep their own household flock in a separate workspace.
-- Billing should attach to the household workspace, not the user account.
-- Rescue workspaces stay on the free plan.
-- Shared access is controlled by workspace roles like `owner`, `manager`, `staff`, and `viewer`.
+- One user can belong to multiple flocks.
+- A rescue member can also keep their own household flock separate from the rescue flock.
+- Billing should attach to the household flock, not the user account.
+- Rescue flocks stay on the free plan.
+- Shared access is controlled by flock roles like `owner`, `assistant`, `caregiver`, and `viewer`.
 - FlockPal no longer stores local passwords.
 - Authentication now happens through magic links or external identity providers.
 
@@ -96,6 +96,6 @@ Set these if you want magic links delivered by email instead of logged as a prev
 
 ## Notes for monetization and security
 
-This starter now includes the account and workspace foundation for monetization, but it still needs production-grade session hardening, invitation verification, billing integration, audit logging, and background reminder delivery before launch.
+This starter now includes the account and flock foundation for monetization, but it still needs production-grade session hardening, invitation verification, billing integration, audit logging, and background reminder delivery before launch.
 
-For account design, `standard` vs `rescue` is best treated as a workspace type, not as a user role. If paid plans are added later, a separate `admin account mode` is usually less flexible than workspace roles such as `owner`, `manager`, `staff`, and `viewer`. That lets the same underlying account system work for both households and rescues without splitting product logic into unrelated account classes.
+For account design, `standard` vs `rescue` is best treated as a flock type, not as a user role. If paid plans are added later, a separate `admin account mode` is usually less flexible than flock roles such as `owner`, `assistant`, `caregiver`, and `viewer`. That lets the same underlying account system work for both households and rescues without splitting product logic into unrelated account classes.