Invitations and Onboarding
Why invitations matter
Section titled “Why invitations matter”Sicket is permission-sensitive. Invitations are not just convenience emails; they are part of how access is scoped safely.
An invitation determines:
- which organization the user belongs to
- which role they receive
- which building they are attached to, when relevant
Who can invite whom
Section titled “Who can invite whom”Organization admin
Section titled “Organization admin”Organization admins can:
- invite landlords
- invite tenants
- create buildings and assign users into them
Landlord
Section titled “Landlord”Landlords can invite tenants for buildings they are assigned to.
They do not gain access to unrelated buildings through the invitation flow.
Tenant
Section titled “Tenant”Tenants do not invite users.
Tenant onboarding
Section titled “Tenant onboarding”Tenant onboarding is stricter than staff onboarding because tenant scope must match an actual residence.
When a tenant accepts an invitation:
- the invitation defines the organization and building
- the tenant creates an account
- the tenant is linked to one residential unit
That unit can be selected or created during acceptance depending on the flow.
Landlord onboarding
Section titled “Landlord onboarding”When a landlord accepts an invitation, their account becomes active in the assigned building scope.
A landlord can later be associated with multiple buildings through assignments.
Why this design matters
Section titled “Why this design matters”This onboarding model prevents common access mistakes, such as:
- a tenant seeing another building
- a landlord drifting into the wrong building
- users being created without a clear operational scope