Review queue
Opening the review queue Navigate to Approvals in the sidebar (team context). Members with property approve and/or request approve permission land on the Review queue by default. The queue lists change proposals awaiting decision — newest or most urgent first depending on sort. If you lack reviewer permission, you will not see this view; use My submissions instead. Queue layout Each proposal card summarizes: Entity type — listing or buyer request Change type — create, update, delete Title or tracking reference Proposed by — submitting agent Status — pending, approved, rejected (historical tabs may show past items) Stale indicator when underlying data drifted Click Review to open the detail dialog with full field diffs. Review dialog Inside the dialog you see: Proposed changes — side-by-side or before/after field list Delete proposals — explicit warning when record would be removed Optional review note — visible to submitter; use for reject reasons Actions: Approve — applies the change immediately Reject — declines; prior approved version remains Confirm carefully on deletes — recovery may require archive restore or recreate. Tabs and filters Toolbar controls narrow the queue: View tabs Properties vs Requests entity filter Status — pending (default for active work), approved, rejected history Search and filters Search by title text Change type — create / update / delete / all Out of date only — proposals invalidated by newer edits Use Out of date after busy weekends to clear conflicts first. Working through a long queue Large queues split into pages — watch the summary (“1–20 of 84”). Work oldest pending first if your team policy prioritizes first-in-first-out. Notifications integration Reviewers receive change pending approval notifications when agents submit. Click through to open the exact proposal in the queue. Clear notifications after review to keep the bell manageable. Approval best practices Creates — Verify photos, price sanity, amenity completeness, correct transaction type. Updates — Focus on price, status, and legal-sensitive fields; typos in description may approve fast. Deletes — Confirm listing actually sold/withdrawn; accidental delete proposals happen. Notes — On reject, always leave a note agents can act on. Throughput tips Dedicated review slot daily beats letting queue exceed 48 hours Filter Requests separately if property volume drowns tenant leads Pair junior submits with senior reviewer during training weeks After approve/reject Submitter gets notification. Approved changes reflect on lists immediately unless search index lags seconds. Rejected proposals disappear from pending badges on records. Activity history entries help settle “who approved the price drop?” later. Permissions edge cases Reviewers need approve permission per entity type — property approve alone does not cover buyer requests. Owners grant both to office managers commonly. If approve button missing, you are view-only — ask role update. The review queue is the quality gate protecting your brand in market — treat it with the same urgency as client callbacks.
Was this guide helpful?