Workflow: Organization Admin

1. Set up the organization structure

Organization admins are the main customer operators inside Sicket.

A typical first step is to create the operational structure:

• create buildings
• review plan limits
• create or manage residential units where needed
• assign landlords to the correct buildings

This step defines the foundation for everything else in the product.

2. Invite the right people

Organization admins can invite:

• landlords
• tenants

This is the main control point for bringing users into the system with the correct scope from the start.

3. Monitor operations

Once the organization is active, the admin usually works across:

• ticket queues
• announcements
• analytics
• knowledge-base content
• user and building management

This role is the broadest customer-facing operational role in Sicket.

4. Manage quality and communication

Organization admins can:

• review ticket handling across buildings
• publish announcements
• manage knowledge-base entries
• use analytics to spot volume and recurring issues

This makes the role both administrative and operational.

5. Control growth against the plan

Because subscription plans affect capacity and features, organization admins also need to understand:

• unit limits
• feature gating
• which workflows are enabled on the current plan

For example, the knowledge base and some advanced support workflows depend on plan level.

6. Keep scope clean

Even though organization admins are broad in scope, they still operate inside one organization.

They do not become platform admins, and they do not automatically gain access outside the organization workspace.

Typical outcomes this role owns

An organization admin is usually responsible for:

• correct building setup
• correct user onboarding
• consistent ticket handling
• announcement quality
• knowledge-base quality
• operational visibility through analytics