Skip to content

Organizations, Buildings, and Units

An organization is the top-level customer workspace in Sicket.

It contains:

  • buildings
  • users and memberships
  • invitations
  • announcements
  • tickets
  • analytics
  • knowledge-base content
  • subscription plan state

If a customer manages multiple buildings, they are usually grouped inside one organization.

Buildings are the main operational scope for day-to-day work.

A building can have:

  • landlords assigned to it
  • tenants assigned to units inside it
  • building-scoped announcements
  • building-scoped tickets
  • building-scoped analytics
  • building-scoped knowledge-base entries

Many staff permissions are validated at building level rather than only at organization level.

Residential units represent the tenant’s concrete living space inside a building.

This is important because Sicket uses units to enforce resident scope.

Current rule:

  • a tenant must belong to exactly one residential unit

That unit is typically created or selected during invitation acceptance.

Organization admins can assign people across the organization.

Landlords can be assigned to multiple buildings.

This lets one landlord operate across a portfolio without gaining organization-wide admin rights.

Tenants do not float between buildings.

Their account is tied to one residential unit, which indirectly ties them to one building.

This structure affects:

  • who can create a ticket
  • which tickets a user can see
  • who can invite whom
  • who can read a knowledge-base entry
  • which analytics a landlord can open

If scope data is wrong, the rest of the product becomes unsafe. That is why Sicket treats organizations, buildings, and units as core access-control objects rather than just labels.