ldraney/landscaping-assistant
1
0
Fork 0
Code Issues 32 Pull requests 1 Projects Releases Packages Wiki Activity Actions 4

Update docs for four-role model, tab layout, and multi-tenancy #119

New issue
Closed
opened 2026-06-06 13:05:19 +00:00 by ldraney · 0 comments
ldraney commented 2026-06-06 13:05:19 +00:00
Owner
Copy link

Type

Spike

Lineage

Related to ldraney/landscaping-assistant #107 (auth). Supersedes #113 (original user stories doc). Documents the expanded role model, navigation design, and onboarding flow decided in the 2026-06-05/06 planning sessions.

Repo

ldraney/landscaping-assistant

Question

What is the complete user model, navigation structure, and onboarding flow for a multi-tenant landscaping app with four roles (Client, Crew Member, Crew Lead, Admin)?

What to Explore

  • Map real-world users (Lucas, Devin, homeowners, future crew) to app roles
  • Define tab visibility per role with centered person icon
  • Design solo-to-business onboarding flow
  • Update all docs (ROADMAP, architecture, README, user stories) to reflect decisions

Success Criteria

  • All docs accurate and consistent with the four-role model
  • Tab layout documented with person icon centered in slot 3
  • Onboarding flow documented (solo client default, join-a-crew request)
  • Data model updated for multi-tenancy (Business, UserBusiness, per-user queues)
  • Lucas approves before ticketing proceeds

Time-box

1 session.

Related

  • #107 -- parent auth issue
  • #113 -- original user stories doc (superseded)
  • #115, #116, #117, #118 -- implementation tickets that depend on this doc
### Type Spike ### Lineage Related to `ldraney/landscaping-assistant #107` (auth). Supersedes #113 (original user stories doc). Documents the expanded role model, navigation design, and onboarding flow decided in the 2026-06-05/06 planning sessions. ### Repo `ldraney/landscaping-assistant` ### Question What is the complete user model, navigation structure, and onboarding flow for a multi-tenant landscaping app with four roles (Client, Crew Member, Crew Lead, Admin)? ### What to Explore - Map real-world users (Lucas, Devin, homeowners, future crew) to app roles - Define tab visibility per role with centered person icon - Design solo-to-business onboarding flow - Update all docs (ROADMAP, architecture, README, user stories) to reflect decisions ### Success Criteria - [ ] All docs accurate and consistent with the four-role model - [ ] Tab layout documented with person icon centered in slot 3 - [ ] Onboarding flow documented (solo client default, join-a-crew request) - [ ] Data model updated for multi-tenancy (Business, UserBusiness, per-user queues) - [ ] Lucas approves before ticketing proceeds ### Time-box 1 session. ### Related - #107 -- parent auth issue - #113 -- original user stories doc (superseded) - #115, #116, #117, #118 -- implementation tickets that depend on this doc
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
docs/update-app-architecture
revert-213
move-other-crew-bottom-remove-schedule
feature/today-view-improvements
154-enable-assume-ssl
revert-145-person-icon
docs/user-stories-auth
docs/update-infra-pipeline-post-incident
fix-cache-step-blocking-deploy
fix-kaniko-registry-pull
deactivate-from-today
feature/quick-address-entry
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/landscaping-assistant#119
No description provided.