Privacy and visibility
Visibility depends on role, building scope, ticket type, and anonymous settings.
Staff visibility
Section titled “Staff visibility”Authorized staff can see operational information needed to manage the building, including ticket details, tenant names, and unit information where relevant.
Tenant visibility
Section titled “Tenant visibility”Tenants see their own tickets, building communications, and community tickets they are allowed to view.
Tenants should not see another tenant’s residential unit information on community tickets.
Anonymous tickets
Section titled “Anonymous tickets”Anonymous posting hides the tenant identity from other tenants. Staff can still see the information needed to manage the issue.
If a tenant views their own anonymous community ticket, Sicket may identify it as their own ticket without exposing that identity to others.
Building separation
Section titled “Building separation”Tenants should not see content from buildings they do not belong to.
Landlords should only see assigned building data unless they also have broader organization permissions.
Observers should only receive read-only access to assigned building data. They should not be able to change records or create new operational work.
Incidents
Section titled “Incidents”Tenants only see incidents after staff publish them to residents.
Tenants can see linked community tickets and visible announcements where they already have access.
Tenants should not see linked personal tickets, staff summaries, internal notes, source pattern evidence, or contractor packets.
Contractor cases
Section titled “Contractor cases”Contractor cases are not normal Sicket accounts.
Contractors can only see the selected information in the protected packet. Staff should only include the minimum information needed for the contractor to complete the work.