Workflow: Landlord
1. Accept invitation and enter assigned scope
Section titled “1. Accept invitation and enter assigned scope”A landlord is invited into one or more building scopes.
After account creation, the landlord can work only inside buildings they are assigned to.
This matters because the landlord role is building-scoped, not organization-wide by default.
2. Review incoming tickets
Section titled “2. Review incoming tickets”A landlord’s daily work usually starts in ticket lists and building dashboards.
They can:
- view tickets for assigned buildings
- review status and operational load
- inspect ticket history, comments, attachments, and internal notes
They cannot view unrelated buildings.
3. Manage tickets operationally
Section titled “3. Manage tickets operationally”For tickets in scope, a landlord can:
- update ticket details where allowed
- change ticket status
- add comments
- add internal notes for staff-only context
- use AI draft replies to speed up communication
Internal notes are especially important for landlord workflows because they preserve operational context without exposing it to tenants.
4. Invite tenants for assigned buildings
Section titled “4. Invite tenants for assigned buildings”Landlords can invite tenants into the buildings they manage.
This lets them onboard residents without getting broader organization-admin rights.
The invitation flow still preserves the tenant’s final unit-level scope.
5. Use building-scoped insights
Section titled “5. Use building-scoped insights”Landlords can work from:
- a single-building dashboard
- aggregate views across their assigned buildings
This supports portfolio-level oversight without exposing unrelated buildings.
6. Use knowledge and announcements where allowed
Section titled “6. Use knowledge and announcements where allowed”Depending on scope and plan level, a landlord may also:
- create or manage building-scoped knowledge-base entries
- publish or manage announcements in allowed scope
The common principle is the same: building authority, not full organization authority.
What a landlord cannot do
Section titled “What a landlord cannot do”Landlords cannot:
- manage arbitrary buildings outside assignment
- act as an organization admin unless separately granted that role
- bypass building-level scope controls
Sicket treats landlord access as operationally broad, but still bounded.