Glossary
Use this glossary when a tutorial uses a Sicket product term.
Organization
Section titled “Organization”The housing association, property company, or operations team using Sicket.
Building
Section titled “Building”A physical building managed inside an organization. Most tenant-facing content is building-scoped.
A residential unit, apartment, or home inside a building.
Current scope
Section titled “Current scope”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.
Organization admin
Section titled “Organization admin”A staff user who manages organization settings, buildings, users, billing, and plan limits.
Landlord
Section titled “Landlord”A staff user assigned to one or more buildings. Landlords can manage building-related work for their assigned buildings.
Observer
Section titled “Observer”A read-only building stakeholder. Observers can view assigned building information but cannot take operational actions.
Tenant
Section titled “Tenant”A resident user assigned to a building and unit.
Ticket
Section titled “Ticket”A tenant request or report that staff can review, comment on, assign status to, and resolve.
Personal ticket
Section titled “Personal ticket”A ticket visible to the tenant who created it and staff. Other tenants do not see it.
Community ticket
Section titled “Community ticket”A ticket visible to tenants in the same building when community visibility is enabled. Staff can still see full details.
Announcement
Section titled “Announcement”A building-scoped staff message that can be shown in Sicket and optionally sent by email.
News post
Section titled “News post”A building-scoped update intended for broader resident communication.
Knowledge base entry
Section titled “Knowledge base entry”A reusable answer written by staff. Sicket can suggest relevant entries during ticket creation, and tenants can view them on the Knowledge Base page.
Incident
Section titled “Incident”A larger building issue coordinated by staff. Incidents can group related tickets, announcements, patterns, contractor cases, internal notes, and resident-facing updates.
Contractor case
Section titled “Contractor case”A protected share packet that gives an external contractor selected ticket or incident information through a link and access code.
Next action
Section titled “Next action”A ticket follow-up state that explains what a ticket is waiting for and optionally when staff should follow up.
QR self-join request
Section titled “QR self-join request”A tenant request started from a building QR code. After email verification, staff must approve the request before the tenant can access the building.