Skip to content

Work / DwarSeva / Wiki / Entities

visitor-request

Entitycanonicalverified 2026-10-04

VISITOR.REQUEST

Summary

One request for a visitor to enter a unit, from creation to check-out.

Canonical values

Key Value Last changed
STATUS.ENUM PENDING, APPROVED, REJECTED, CHECKED_IN, CHECKED_OUT, EXPIRED, CANCELLED 2026-10-04
LABEL.PENDING Pending 2026-10-04
LABEL.APPROVED Approved 2026-10-04
LABEL.REJECTED Rejected 2026-10-04
LABEL.CHECKED_IN Inside 2026-10-04
LABEL.CHECKED_OUT Checked Out 2026-10-04
LABEL.EXPIRED Expired 2026-10-04
LABEL.CANCELLED Cancelled 2026-10-04
CREATE.RESIDENT create-visitor.tsx — name and purpose required; phone, vehicle, count optional; arrival typed as text 2026-10-04
CREATE.GUARD guard "New Entry" tab — name, phone, unit and purpose required; arrival is now 2026-10-04
PURPOSE.GUARD delivery, guest, service, meeting, other 2026-10-04
PURPOSE.RESIDENT free text 2026-10-04
MOVE.PENDING→APPROVED resident or society admin (detail screen); guard (list card or detail) 2026-10-04
MOVE.PENDING→REJECTED same actors; the detail screen asks for an optional reason 2026-10-04
MOVE.APPROVED→CHECKED_IN guard 2026-10-04
MOVE.CHECKED_IN→CHECKED_OUT guard 2026-10-04
BUCKET.EXPECTED PENDING, APPROVED 2026-10-04
BUCKET.HISTORY CHECKED_IN, CHECKED_OUT, REJECTED, CANCELLED, EXPIRED 2026-10-04
PUSH.CATEGORY visitor_request, with actions Approve and Reject 2026-10-04

Nothing in the three apps sets EXPIRED or CANCELLED; they exist in the schema and the badge.

A guard can approve a visitor. The guard's list shows Approve and Reject on a PENDING card. Whether a guard should be able to admit someone the resident has not answered for is a product decision nobody has written down.

Related

Sources

  • packages/db/prisma/schema.prisma
  • apps/mobile/src/app/visitor-requests/[id].tsx
  • apps/mobile/src/app/(roles)/guard/(tabs)/visitors.tsx
  • apps/mobile/src/components/visitor/VisitorStatusBadge.tsx
  • apps/mobile/src/lib/enums.ts
  • apps/mobile/app.json