What organization administrators can do in Sicket

The organization administrator is the account responsible for setting up and governing a Sicket organization. It combines portfolio-wide operational access with plan, billing, user, and organization settings.

This role is appropriate for an owner, internal administrator, or central housing team that needs the complete organizational overview. Day-to-day building work can still be delegated to landlords without giving those users billing or unrelated-building access.

Organization setup and plan ownership

Organization administrators create the organization, choose or change the plan, and manage billing through Sicket and the Stripe customer portal where applicable. They can review current limits for buildings, managed homes, landlords, observers, attachment storage, and Knowledge Base entries.

Home capacity is organization-wide. A managed vacant home counts, while additional residents sharing one home do not consume more home capacity. Knowledge Base entries belong to buildings, but the allowance is also pooled across the organization; copying an entry to another building consumes another entry.

They also manage organization-level settings, supported security options, AI feature availability, and other configuration that should not be delegated to building staff.

Buildings, residential units, and scope

An administrator can create buildings and maintain their address, display name, accent theme, contact details, residential units, and availability. Buildings provide the main scope for tickets, residents, landlords, communications, incidents, knowledge, and analytics.

Residential units can be added individually, generated from an optional numbering range, or imported from a reviewed CSV file. This avoids requiring a large building to enter every home manually.

When working across a portfolio, the current scope selector is important. An administrator can review all buildings or narrow the dashboard to one building before making a change.

Inviting people and assigning access

Organization administrators can:

• invite tenants individually or in bulk;
• enable and share a building QR code for tenant self-join;
• approve or reject verified home-assignment and QR join requests;
• invite landlords and assign their managed buildings;
• invite other organization staff where supported;
• invite observers and assign one or more buildings for read-only oversight;
• review people, assignments, account state, and tenant move-outs.

Landlord and observer assignments can be changed later. Their scopes remain separate: landlords perform operational work, while observers have privacy-limited read-only access.

An individual invitation can include a home selected by staff. If the resident accepts it unchanged, no separate home-assignment approval request is created. Resident-entered homes, changed preselected homes, email-only bulk invitations, and QR self-join require staff approval after the applicable email-verification steps.

Portfolio-wide operational workflows

Administrators can use the same operational tools available to authorized staff, including tickets, next actions, internal notes, incidents, announcements, News & Updates, banners, Knowledge Base entries, contractor cases, and analytics. Ticket work can be viewed in compact, list, or desktop board layouts with filters and follow-up indicators, while dashboard metrics link back to relevant records.

Only the ticket creator can submit resolution feedback. Authorized administrators can review feedback across tickets in their scope to identify repeated service or communication issues.

They can also review recurring ticket patterns and decide how resident-facing communication is handled. Pattern detection does not automatically publish an incident or notify residents; staff still review the evidence and choose the next step.

Responsibilities that should stay deliberate

Broad access also means broader responsibility. Administrators should:

1. Assign users only to the buildings they need.
2. Verify QR join requests before granting tenant access.
3. Keep residential-unit labels free of unnecessary personal information.
4. Separate tenant-visible comments from internal notes.
5. Review plan limits before inviting users or adding shared Knowledge Base content.
6. Keep billing and organization settings limited to people who own those decisions.

The organization administrator documentation provides the current step-by-step controls. You can also read the landlord role guide, understand tenant access, or follow the first-building setup workflow.