Tickets and privacy
Observers can open ticket overviews for assigned buildings. This supports workload oversight without exposing the full operational case file.
Information you may see
Section titled “Information you may see”- ticket title, description, type, status, priority, and category where allowed
- building and safe location context
- created and updated times
- community conversation activity where it is part of the resident-visible record
- public status history that is safe for resident-style viewing
Information kept private
Section titled “Information kept private”Observers cannot see:
- internal notes or staff follow-up notes
- attachment files or their contents
- personal-ticket conversations
- anonymous reporter identities
- the reporter or residential unit on personal tickets
- staff-only timeline events, contractor packets, or source pattern evidence
- staff next-action details and internal workload metadata
An Observer may see that a ticket or attachment exists without being able to open private content.
No ticket actions
Section titled “No ticket actions”Observers cannot create tickets, comment, reply, edit, delete, withdraw, change status, set a next action, link an incident, or share a contractor case.
Why this is limited
Section titled “Why this is limited”Observer access is designed for oversight, not case handling. Use aggregate information to understand building activity, then ask authorized staff when an operational follow-up is needed.