Personal, community, and anonymous tickets in Sicket

Not every housing question should be visible to the same people. A problem inside one home may contain private details, while a broken entrance door can affect everyone in the building. Sicket uses personal and community tickets to make that distinction clear before a ticket is created.

Anonymous submission adds a separate privacy choice for community tickets. It changes how the resident’s identity is shown, but it does not change which staff members are responsible for handling the ticket.

Personal tickets are private from other tenants

A personal ticket is visible to the tenant who created it and to authorized organization staff with access to that building. Other tenants cannot find or open it.

Personal tickets are the appropriate choice for matters that concern one home or may contain private context, such as:

• a repair needed inside an apartment;
• a question about an individual situation;
• information that should not be shared with neighbors;
• attachments or conversations intended only for the resident and responsible staff.

An observer assigned to the building may see a limited, read-only ticket overview. On personal tickets, the reporter name and residential unit are hidden, and the observer cannot open the personal conversation or attachment contents.

Community tickets keep shared issues visible

A community ticket is visible to tenants in the same building. It is intended for a shared issue such as an entrance fault, lift problem, hallway lighting failure, or interruption to a building-wide service.

This visibility helps residents see that an issue is already known. They can follow an active community ticket for updates instead of creating another ticket about the same problem. Other tenants may comment only when comments have been enabled for that ticket. Attachment contents remain limited to the creator and authorized staff.

During ticket creation, Sicket can suggest similar community tickets from the same building. The resident can follow an existing ticket or continue creating a new one when the situation is different or still needs individual attention.

What anonymous means in Sicket

Anonymous submission is available only for community tickets. It hides the creator’s name and residential unit from other tenants and keeps comments from the original creator anonymous in tenant-facing views.

Anonymous does not mean that the ticket has no accountable creator or that nobody can identify the resident. Organization administrators and assigned landlords can still see the identity and unit details required to assess, respond to, and moderate the ticket. Sicket’s internal systems and authorized platform administrators may also process that information to operate and secure the service. Observers do not receive the hidden identity.

This distinction prevents a resident’s identity from being exposed to neighbors while preserving the operational context needed by the housing team.

Choosing the right visibility

Use a personal ticket when the matter applies to one home, contains sensitive context, or needs a private conversation. Use a community ticket when the issue affects shared space or other residents would benefit from seeing its status.

Choose anonymous submission when a community issue should remain visible but the resident does not want their identity shown to other tenants. If the ticket itself includes identifying details in its title or description, those details can still be visible in the ticket content, so residents should avoid adding unnecessary personal information.

Clear boundaries for residents and staff

Ticket visibility is enforced by building membership and role. Tenants stay within their own building, landlords stay within assigned buildings, and organization administrators retain organization-wide operational access. Read-only observer access has additional privacy restrictions.

For the complete resident workflow, read what tenants can do in Sicket. Housing teams can also review the product overview, privacy notice, and observer access guide.