What tenants can do in Sicket

Tenants use Sicket to contact the team responsible for their building, follow ticket progress, and find current building information. Their dashboard is intentionally simpler than the staff dashboard and stays limited to their own building and resident-safe content.

Joining a building

A tenant can join in two ways:

• Invitation: staff send an invitation to a specific email address and building.
• Building QR code: the tenant scans the building’s Sicket QR code, enters account and requested-unit details, verifies the email address, and waits for staff approval.

QR self-join does not grant immediate building access. Organization administrators, or landlords for assigned buildings, review the verified request first. The current steps are documented in the tenant QR self-join guide.

Personal and community tickets

Tenants can create tickets for questions, repairs, and building issues. Sicket separates two visibility types:

• Personal tickets are visible to the tenant who created them and authorized staff.
• Community tickets can be visible to other tenants in the same building when community visibility is enabled.

Community tickets are useful for shared issues such as an entrance problem or lift outage. Personal tickets are the safer choice for matters limited to one home or containing private details.

During ticket creation, Sicket can show relevant active incidents, announcements, Knowledge Base answers, and similar community tickets. These suggestions can answer a question or prevent an unnecessary duplicate, but the tenant can continue creating the ticket when help is still needed.

Following progress and communicating

After a ticket is created, the tenant can review its status and tenant-visible updates. Where discussion is available, the tenant can add comments and attachments. Staff may also use internal notes, but those notes are never shown to tenants.

When a ticket is resolved or closed, its creator may be able to provide resolution feedback. Other tenants following a community ticket cannot submit feedback on behalf of the creator.

Building information tenants can read

Depending on what staff have published, tenants can view:

• active incidents for their building;
• announcements within their active period;
• published News & Updates;
• building banners;
• Knowledge Base entries and recurring answers;
• selected building and home information.

Drafts, archived communications, staff summaries, pattern evidence, and private operational records remain outside the tenant view.

Tenant privacy boundaries

Tenants cannot see another tenant’s residential unit, personal tickets, or attachment files. Community tickets do not expose another resident’s unit. When a community ticket is submitted anonymously, the identity is hidden from other tenants, although authorized staff retain the operational context needed to handle it.

Tenants can also manage supported profile, security, session, and notification settings. A tenant who plans to leave can request a move-out date; staff confirm the request before the building assignment ends.

For the staff side of the workflow, read what landlords can do and what organization administrators can do. Housing teams can use the building onboarding guide to introduce this tenant workflow clearly.