How to get started with Sicket in a building

Sicket can be introduced without replacing rent collection, accounting, or asset-management systems. It focuses on the communication layer: tenant tickets, building updates, recurring answers, and clear follow-up.

A small launch is usually easier to control than importing everything at once. Start with one building, define who handles its communication, invite a test group, and expand after the workflow is understood.

1. Create the building

An organization administrator creates the building from setup or the Buildings page. Prepare the display name, country, street, postcode, city, accent theme, and an optional building image. House numbers and labels are entered later when adding residential homes, not as a building-wide number range.

The display name appears in the dashboard, tenant pages, invitations, and scope selector. Keep it recognizable and short enough to scan. The first-building documentation contains the current field-by-field process.

2. Add residential units and practical building details

Residential units connect tenants to the correct home. Add a unit number and, where useful, a short label such as a floor or wing. Do not place tenant names or unnecessary personal data in unit labels.

For a building with a predictable numbering scheme, use the optional range generator instead of entering every home separately. Existing unit lists can also be reviewed and imported from CSV. Check the preview before importing so duplicate numbers and formatting issues can be corrected first.

Plan capacity counts managed homes across the organization, not resident accounts per building. A vacant home still counts while it remains managed in Sicket. Two or more residents sharing one home use the same home capacity. Read how residential units and shared homes work in Sicket for the complete model.

Review the building contact details and branding that residents will see. This is also a useful moment to decide whether the building needs reusable Knowledge Base answers, a welcome banner, or an initial News & Updates post.

3. Decide who handles the building

A small owner-operated building can remain with the organization administrator. For delegated operations, invite landlords and assign the buildings they manage. Assigned landlords receive building-scoped operational access and become the primary recipients for relevant ticket email.

Use observer accounts only for stakeholders who need read-only oversight. Observers do not handle tickets, manage people, or receive landlord operational routing.

4. Choose how tenants will join

Sicket supports three practical routes:

1. Individual invitations for a known tenant email, optionally with a home selected by staff.
2. Bulk invitations when staff already have a reviewed tenant list. An email-only invitation lets the resident request their home.
3. Building QR self-join when residents should request building and home access themselves.

When an individual invitation already contains a home and the resident accepts that home unchanged, no separate home-assignment approval request is created. A resident-entered home, a changed preselected home, an email-only bulk invitation, or QR self-join requires staff approval. Applicable email-verification steps still happen before access is completed.

For a QR launch, open Invitations, choose the QR code option, select the building, and share or print the code. Each building has its own join destination, so make sure the poster belongs to the correct building.

5. Review home and QR join requests

After scanning the code, a tenant enters account details and requested-unit information, then verifies the email address. The account does not become active immediately.

Staff review the request on the Invitations page. Check the verified person, email, requested unit, building, and join method. Approve the request only when the person belongs in that building; reject incorrect requests and direct the tenant to the correct QR code when needed.

This approval step prevents a publicly visible QR poster from becoming unrestricted building access. The exact workflow is available in the QR request review guide.

Residents who are already active can request a correction when their home assignment is wrong. Moving a resident out ends that person’s occupancy; it does not remove the shared home or end another resident’s access to it.

6. Publish a small amount of useful information

Before announcing the launch, add information that makes the tenant dashboard immediately useful:

• one welcome or launch update;
• any current planned-maintenance announcement;
• a few recurring Knowledge Base answers, such as lost keys or waste collection, if included in the plan;
• an active incident only when a real building-wide issue exists;
• clear contact expectations for urgent situations that should not wait for a normal ticket.

Do not fill the platform with placeholder content. A short set of current, building-specific information is easier for residents and staff to trust.

7. Test the complete route

Before distributing the QR code widely:

1. Create a test tenant invitation or controlled join request.
2. Confirm the building and residential-unit assignment.
3. Create one personal and one community test ticket.
4. Check staff email routing and tenant-visible comments.
5. Verify that internal notes remain staff-only.
6. Resolve the test ticket and inspect the tenant view.

8. Explain the change simply

Residents do not need a long software introduction. Tell them where to scan or sign in, what Sicket should be used for, how urgent emergencies are handled, and that QR access requires verification and staff approval.

For a clearer division of responsibilities, review the guides for organization administrators, landlords, and tenants. Current plans and role availability are listed in the plan comparison.