How residential units and shared homes work in Sicket

Sicket pricing counts homes, also called residential units, rather than tenant accounts. The distinction matters because a physical home and the people currently living there are not the same record.

A residential unit remains part of a building when it is vacant, and more than one resident can share it. This keeps building setup stable when households change without treating every resident as another home.

A residential unit represents a physical home

Each residential unit belongs to one building. It has a unit number and can have an optional label for useful context such as a floor, wing, or internal reference. Unit labels should not contain resident names or other unnecessary personal information.

Residents are connected to their current home through an active occupancy assignment. Two or more co-residents can therefore point to the same residential unit instead of Sicket creating a duplicate home for each person.

The unit can remain active with no residents assigned. That is how a vacant but still managed home stays available for a later invitation or approved join request.

Home capacity is organization-wide

The advertised plan limit applies to active managed homes across the complete organization, not separately to every building:

• Starter includes up to 10 homes;
• Professional includes up to 500 homes in total;
• Enterprise home capacity is configured in the commercial terms.

One active residential unit uses one place in that allowance whether it is vacant, has one resident, or is shared by multiple residents. Adding another resident to the same home does not use another place.

Staff can edit a home’s number and optional label. Removal is only available for unused homes with no active residents, pending invitations or home requests, or linked records such as tickets and occupancy history. Moving the last resident out does not make a home with historical records removable. This protects the history of the building and its residents.

Review the current numbers in the plan comparison and the fuller explanation under home capacity.

Homes can be added without entering every one manually

Staff can add a residential unit individually. For buildings with predictable numbering, the setup flow can generate all, odd, or even numbers in a range, with optional prefixes, suffixes, and number padding. An existing list can also be imported from CSV after staff review a preview for duplicates, invalid rows, and plan-limit conflicts. Each batch supports up to 2,000 rows, and duplicates are skipped.

Within one building, each normalized unit number identifies one home. Optional labels can add useful building context, but the number should remain recognizable to both residents and staff.

Invitations determine when approval is needed

An individual tenant invitation can contain a home selected by staff. When the invited resident accepts that home unchanged, no separate home-assignment approval request is created, although applicable email-verification steps still apply.

Staff approval is required when:

• a resident enters a home themselves;
• a resident changes the home preselected in an invitation;
• an email-only bulk invitation does not specify the home;
• a resident joins through a building QR code.

During approval, authorized staff can select an existing residential unit or create the requested home when it is valid and the plan has capacity. This prevents a public QR code from granting unchecked access to a building or home.

Corrections and move-outs affect the resident, not the shared home

An existing resident can request a correction when the assigned home is wrong. Once authorized staff approve a different home, the resident’s previous occupancy ends and the new assignment becomes active.

Moving out follows the same separation. It ends that resident’s occupancy and access. It does not delete or archive the residential unit, and it does not remove another resident who shares the home.

Sharing a home does not share personal tickets

The residential-unit assignment gives Sicket the building and home context needed for resident access and ticket handling. It does not make personal tickets visible to co-residents. Personal conversations and attachment contents remain restricted to the creator and authorized operational staff. Assigned observers can see a limited ticket overview, including its title and description, without reporter-name or home fields; they cannot open private conversations or attachments.

Community tickets follow the building-wide visibility rules instead. Read the guide to personal, community, and anonymous tickets for those privacy boundaries.

For the complete launch sequence, continue with how to get started with Sicket in a building or review what tenants can do in Sicket.