Roles and Permissions
If you are choosing a guide by role, start with the Customer Overview and then open the guide for your role. This page is the permission reference.
Platform admin
Section titled “Platform admin”Platform admins exist above any single organization.
They can:
- manage and inspect data across organizations
- access platform-level administration
- bypass normal organization-level visibility restrictions where the backend allows platform admin scope
This role is for internal Sicket administration, not for normal customer users.
Organization admin
Section titled “Organization admin”Organization admins are the highest customer-level role inside an organization.
They can:
- create and manage buildings
- invite landlords and tenants into the organization
- manage tickets across the organization
- publish announcements
- manage knowledge-base entries
- access organization-wide analytics
- manage building assignments
Organization admins are the primary operational owners of a Sicket workspace.
Landlord
Section titled “Landlord”Landlords operate inside one or more assigned buildings.
They can:
- view and manage tickets for their assigned buildings
- add internal ticket notes
- invite tenants for buildings they are assigned to
- create and manage some building-scoped content, such as knowledge-base entries in their scope
- access building-level analytics and aggregate analytics for their assigned buildings
They cannot:
- access unrelated buildings
- manage the entire organization unless they are also an organization admin
- act as a tenant inside multiple units through the landlord role
Tenant
Section titled “Tenant”Tenants are resident users and have the narrowest scope.
They can:
- accept an invitation and create an account
- belong to exactly one residential unit
- create tickets for their building and unit
- view tickets they are allowed to see
- read tenant-visible announcements
- use tenant-safe self-service support features
They cannot:
- manage buildings
- manage knowledge-base content
- create internal notes
- access analytics
- access other buildings
Scope rules that matter most
Section titled “Scope rules that matter most”Tickets
Section titled “Tickets”- only tenants create tickets
- staff can manage tickets in scope
- ticket visibility depends on ticket type and building scope
Buildings
Section titled “Buildings”- organization admins create buildings
- landlords can belong to multiple buildings
- tenants are restricted to one unit and its building
Knowledge base
Section titled “Knowledge base”- organization admins manage organization-wide content
- landlords can only manage building-scoped entries within assigned buildings
- tenants do not manage content
Why Sicket is strict about scope
Section titled “Why Sicket is strict about scope”Most customer trust in Sicket depends on predictable boundaries:
- residents should not see unrelated building data
- landlords should not drift outside their assigned buildings
- organization admins need broad control without becoming platform admins
The product is designed around those boundaries.