Organization Owner or Admin
This guide is for the people responsible for getting Sicket running well inside one organization.
In the product, the actual customer role is Organization Admin. In practice, this is often also the organization owner or the main operations lead.
What this role is responsible for
Section titled “What this role is responsible for”An organization owner or admin usually owns:
- building setup
- user onboarding
- landlord assignments
- tenant rollout
- Ticket quality and visibility
- Announcements
- Knowledge Base quality
- plan usage and feature availability
Typical first steps
Section titled “Typical first steps”1. Create the building structure
Section titled “1. Create the building structure”Start by creating the buildings your organization wants to manage.
This is the foundation for almost everything else in Sicket.
2. Review plan limits
Section titled “2. Review plan limits”Before scaling rollout, check:
- building limits
- unit limits
- whether the Knowledge Base is enabled
- whether other advanced workflows are available on the current plan
3. Invite landlords and tenants
Section titled “3. Invite landlords and tenants”Organization admins can invite:
- landlords
- tenants
This is the main way to bring the right people into the right scope from the start.
Day-to-day work in Sicket
Section titled “Day-to-day work in Sicket”Once setup is complete, this role usually works across:
- Tickets across the organization
- Announcements
- building setup and changes
- landlord and tenant access
- Knowledge Base content
- analytics and plan usage
What to review regularly
Section titled “What to review regularly”To keep the workspace healthy, review:
- whether landlords are assigned to the right buildings
- whether tenant onboarding is landing in the right building and unit
- whether Tickets are being handled consistently
- whether Announcements are reaching the right audience
- whether Knowledge Base content answers common resident questions