User Flow

Owner: Product Design
Reviewers: Product, Engineering, QA
Status: Draft
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per UX milestone

Confirmed Role Entry Points

Role Web/Mobile Flow Status
Admin Login, manage users, farms, ponds, tickets, reports and dashboard. PARTIAL
Owner Login, view dashboard/farms/reports; mobile owner tabs exist. PARTIAL
Manager Login and access operational views where enabled. PARTIAL
Technician Mobile technician home, incidents, notifications and profile. PARTIAL
Viewer/Owner-facing user Mobile farm/activity view patterns exist in current code. PARTIAL

Common Flow

  1. User authenticates.
  2. App resolves role and redirects to role-appropriate home.
  3. User accesses allowed farm/pond data.
  4. User performs operational action such as viewing dashboard, managing entity, logging activity, handling ticket or exporting report.
  5. System records relevant activity and updates downstream notifications where implemented.

Detailed SRS Flows

Global Flow

  1. Login.
  2. Validate credentials/session.
  3. Load role, permission and farm/pond/ticket scope.
  4. Open dashboard.
  5. Select farm and pond.
  6. Open pond detail.
  7. Monitor water metrics, device status and farming logs.
  8. If normal, continue monitoring and daily logging.
  9. If warning/alert, open alert detail, acknowledge, take action and close.
  10. If device issue, create or open ticket, assign, process and close.
  11. If help is needed, open handbook/chatbot, receive recommendation and create ticket when needed.

Alert Handling Flow

  1. Sensor, device or user event occurs.
  2. System evaluates rule or threshold.
  3. System creates alert if condition matches.
  4. System sends notification/email to recipients where configured.
  5. User opens alert detail and acknowledges.
  6. User adds note, controls device, creates ticket or consults handbook/chatbot.
  7. User updates status to in-progress or closed.
  8. System logs all actions.
  9. If timeout/SLA is reached, system escalates.

Ticket Flow

  1. User detects issue.
  2. User creates ticket with pond/device/description/attachment.
  3. System sends email to configured technical recipients.
  4. Admin or system assigns technical staff.
  5. Technical staff accepts ticket, reviews pond/device context, updates progress and closes ticket.
  6. System records SLA metrics and sends status notification.

Chatbot Flow

  1. User opens chatbot.
  2. User selects pond context if applicable.
  3. User enters question or uploads image.
  4. System validates permission.
  5. Chatbot retrieves approved handbook content and permitted pond data.
  6. Chatbot responds with recommendation, confidence and references.
  7. If confidence is low or risk is high, chatbot suggests KTV contact or ticket creation.
  8. User rates response or creates ticket.
  9. Conversation is stored according to retention policy.

Design References

  • ../current/architecture/web-architecture.md
  • ../current/architecture/mobile-architecture.md
  • ../reference/product/[AquaX] User Flow.docx
  • ../reference/design/Danh sách màn hình theo role.docx
  • screen-list.md