Skip to content

Workflow: Launching a New Organization

Before setup starts, confirm:

  • which subscription plan the organization is on
  • how many buildings and units are expected
  • which features should be available from day one

This avoids onboarding the organization into a structure that immediately conflicts with plan limits.

Next, create the buildings that will exist inside the organization.

This is the most important structural step because staff scope, tenant scope, tickets, announcements, and analytics all depend on it.

After the buildings exist:

  • invite or assign organization admins
  • invite or assign landlords to the correct buildings

At this stage, verify that each landlord only sees the buildings they should manage.

Before tenants arrive, make sure the organization is ready for resident-level scope:

  • create units where appropriate
  • verify unit limits against the subscription plan
  • prepare tenant invitation batches

5. Configure communication and support content

Section titled “5. Configure communication and support content”

Before broad tenant rollout, it is usually worth preparing:

  • key announcements
  • initial knowledge-base content
  • basic support and FAQ material

This improves the tenant experience immediately and reduces repetitive tickets.

Once the structure is ready, tenants can be invited in a controlled sequence.

During acceptance, each tenant becomes tied to one residential unit and building scope.

After launch, review:

  • incoming ticket volume
  • whether users landed in the correct scope
  • whether announcements and knowledge content are being used
  • whether the current plan still fits the organization

This is usually when early operational adjustments happen.

Treat launch as a scope-and-quality exercise, not only a technical setup exercise.

If buildings, units, and roles are correct, the rest of Sicket behaves predictably. If that foundation is wrong, the operational experience degrades quickly.