PRODUCT DOCS
Conversation access, inbox controls and message states
Understand membership, personal inbox changes and the limits of delivery/read information.
Access follows the conversation
A connection request and an accepted connection are distinct. Conversation access requires its permitted relationship/membership, not simply a landlord/tenant label. Group administration, leaving a group and direct-contact controls apply only to the offered conversation type and role. Sharing a rental item does not grant access to the item’s private record.
Message and inbox states
These describe app events and personal controls, not legal delivery.
| State or control | Meaning |
|---|---|
| Sending / pending | The client has not yet confirmed a stored send. |
| Failed | That send needs its offered retry/recovery. |
| Stored message | The conversation returned the message. |
| Read information | The supported participant read marker was recorded; it is not formal-service evidence. |
| Mute | Changes the supported notification preference for your conversation. |
| Archive / restore | Moves your conversation between inbox views. It does not remove other members’ history. |
Replies, reactions and shared cards
Replies refer to a conversation message; reactions and pins provide context rather than agreement execution. A shared listing/inspection/application/lease card has its own current state and access requirements. Check that actual record before acting. An image attachment is private conversation content, not automatically public listing media.
Failure and duplicate prevention
A send can appear pending while the client refreshes. The supported retry path preserves its send identity; reopening the conversation helps determine whether it already arrived. A failed refresh does not prove an empty history. Search/history pagination can show a partial view; use its offered older-message controls and clear filters before concluding a conversation is missing.
Retention and safety boundaries
Blocking, group departure, removal, archive and mute have different effects; none promises erasure of all retained evidence. Use the exact confirmation shown for removal. Do not share invitation codes or private download URLs. In-app messages, notifications and read markers do not decide valid notice service, consent to entry or contractual acceptance. External email/push delivery remains governed by its separate release gates.
Product guidance, not legal advice or a guarantee of compliance. For jurisdiction-specific requirements, check current official guidance or obtain advice for your circumstances.