Skip to content

Tickets

Choose Personal if the issue is private or inside your unit.

Choose Community if the issue affects shared building areas and may be useful for other tenants to see.

If unsure, choose Personal.

Suggested answers did not show the result I expected

Section titled “Suggested answers did not show the result I expected”

Continue creating the ticket. Suggested answers are helpful shortcuts, not required.

Staff can still review the issue.

Similar tickets did not find a matching ticket

Section titled “Similar tickets did not find a matching ticket”

Continue creating the ticket if you believe staff need to know.

Try using specific issue words in the title and description, such as elevator, leak, heating, access, or cleaning.

Ticket discussion may be disabled, the personal ticket may belong to another tenant, or the ticket may be resolved, closed, withdrawn, or deleted.

Check:

  • file type
  • file size
  • whether the file is damaged
  • whether the organization has enough attachment storage available

That is expected. Community tickets should not expose residential unit information to tenants.

I can see an attachment count but not the files

Section titled “I can see an attachment count but not the files”

That is expected when you are not the ticket creator. Only the creator and authorized operational staff can open attachment files. Other tenants and Observers see the count only.

Check Current scope and clear filters that do not match the selected building. Invalid query values are removed rather than applied. Use the filter controls to create a valid URL.

Read all did not change another user’s view

Section titled “Read all did not change another user’s view”

Read state belongs to each user. Read all marks every matching record as read for your own account, not for everyone in the building.