What landlords can do in Sicket

A landlord in Sicket is an operational staff user for one or more assigned buildings. The role gives someone enough access to handle day-to-day building communication without giving them organization-wide billing or configuration rights.

This distinction matters when a portfolio has local managers, external managing agents, or different people responsible for different buildings. The organization administrator keeps the full overview, while each landlord works inside a defined building scope.

Assigned buildings define the scope

An organization administrator invites the landlord and assigns one or more buildings. The landlord can switch between those buildings or select an available combined scope. Buildings outside that assignment are not available.

Assignments can be changed later when responsibilities change. This is more controlled than sharing one general staff account and more practical than forwarding every resident email to the organization administrator.

What landlords can manage

Within assigned buildings, landlords can generally:

• review, update, and resolve tenant tickets;
• use tenant-visible comments and staff-only internal notes;
• review relevant tenant details and residential-unit context;
• invite tenants and review QR self-join requests;
• manage resident-facing incidents, announcements, News & Updates, and banners where enabled;
• create protected contractor cases for selected work;
• manage building Knowledge Base entries when the plan supports them;
• review building analytics and operational trends;
• manage supported building details or branding where permitted.

Exact controls still depend on the selected building, organization configuration, record state, and plan. For example, an archived announcement is retained for staff history but is no longer resident-facing.

Ticket responsibility and email routing

Assigned landlords become the primary operational contacts for their buildings. Building-related ticket email routing goes to assigned landlords first. Organization administrators act as the fallback when a building has no assigned landlord.

This keeps routine work close to the person responsible for the building while preserving organization-level oversight. The practical workflow is covered in the Sicket landlord documentation.

What landlords do not control

Landlords do not receive unrestricted organization access. They generally cannot manage:

• organization billing and subscriptions;
• organization-wide legal or security settings;
• AI configuration reserved for organization administrators;
• buildings that have not been assigned to them;
• invitations for other landlords, organization administrators, or Observers.

Use an organization administrator account when someone owns setup, billing, and portfolio-wide configuration. Use Observer access when a stakeholder only needs read-only oversight and should not handle operational work.

A practical way to introduce the role

Before inviting a landlord, decide which buildings they manage and who should receive operational email. After the invitation is accepted:

1. Confirm the assigned buildings in the scope selector.
2. Review open tickets and pending tenant join requests.
3. Agree when to use comments, internal notes, incidents, and announcements.
4. Check which Knowledge Base and analytics features are available on the plan.
5. Keep organization-level billing and configuration with the organization administrator.

See how organization administrators work in Sicket, follow the building setup guide, or compare landlord availability in the plan comparison.