Skip to content

Glossary

Use this glossary when a tutorial uses a Sicket product term.

The housing association, property company, or operations team using Sicket.

A physical building managed inside an organization. Most tenant-facing content is building-scoped.

The home connected to a tenant account. Depending on the country or property, this can represent an apartment, flat, house, room, or suite. Sicket stores a unit number and an optional label so staff can identify it clearly.

The building or All Buildings view selected in the dashboard sidebar. Scope affects which tickets, announcements, news posts, people, analytics, and settings you are currently viewing.

A staff user who manages organization settings, buildings, users, billing, and plan limits.

A staff user assigned to one or more buildings. Landlords can manage building-related work for their assigned buildings.

A privacy-limited, read-only building stakeholder. Observers can view safe information for assigned buildings but cannot take operational actions or view resident rosters and private case content.

A resident user assigned to a building and unit.

A tenant request or report that staff can review, comment on, assign status to, and resolve.

New means the record has not been opened. New update means activity was added after it was last viewed. Opening the record or using Read all clears the state for that user.

A ticket visible to the tenant who created it and staff. Other tenants do not see it.

A ticket visible to tenants in the same building when community visibility is enabled. Staff can still see full details.

A building-scoped staff message that can be shown in Sicket and optionally sent by email.

A building-scoped update intended for broader resident communication.

A reusable answer written by staff. Sicket can suggest relevant entries during ticket creation, and tenants can view them on the Knowledge Base page.

A larger building issue coordinated by staff. Incidents can group related tickets, announcements, patterns, contractor cases, internal notes, and resident-facing updates.

A protected share packet that gives an external contractor selected ticket or incident information through a link and access code.

A ticket follow-up state that explains what a ticket is waiting for and optionally when staff should follow up.

A short, high-visibility message shown for one building while enabled.

A tenant request started from a building QR code. After email verification, staff must approve the request before the tenant can access the building.