Skip to main content
Selora Homes Selora Homes

Multi-property management

Manage a portfolio of Selora homes from one account — group, monitor, update, and delegate access across properties.

Roadmap Multi-Property Management Connect

Summary

Today Selora is built around one account, one owner, one home. That model works for a single household, but a meaningful share of our real customers do not work that way: a property manager operates dozens of rental units, a developer runs a portfolio of show homes and estate homes, an installer supports every home they have ever installed.

As things stand, those customers juggle a separate owner account per property, log in home by home to check status, and share credentials to let staff help — which is a privacy and security problem as much as a usability one. This roadmap entry makes Selora portfolio-grade: one manager account holds many properties, each property keeps its own identity and privacy, and the customer gets the overview, bulk operations, and delegated access that running a portfolio actually requires.

The problem

  • No portfolio view. A manager with 40 homes cannot see at a glance which are online, which raised alerts, or which need attention — every check means logging into a separate account
  • No way to act in bulk. Pushing an update, a recipe, or a configuration change means repeating the same action N times, once per home
  • Shared credentials as a workaround. Letting staff help means sharing owner logins — with no per-property scope, no roles, and no audit trail of who did what
  • Handoffs are messy. Moving a property to a new tenant or buyer is a manual process that leaves the previous owner’s configuration behind

What’s included

One account, many homes

  • Portfolio model: multiple properties under a single manager account; each property keeps its own home identity, automations, and data
  • Property groups: organize properties by region, client, or project, and filter the portfolio view by group

Portfolio dashboard

  • Cross-property health and alerts: aggregated status, active alerts, and connectivity across all properties with priority-based filtering, drill-down to the individual home
  • Export: standardized status and sensor data available through Selora Connect for external reporting

Bulk operations

  • Apply at scale: configuration updates, recipe changes, and service actions can target a group or the whole portfolio, with per-property results reported back

Delegated access

  • Scoped roles: staff and team members get view-only, support, or full access per property or group — no shared owner logins, with actions recorded in an audit trail
  • Ownership transfer: hand a property to a new owner (tenant, buyer) cleanly, with the previous owner’s configuration reset or preserved per policy

Why it matters

  • Unlocks the professional segment: property managers, developers, and large installers are the customers who buy in volume, and the estate and enterprise tiers only make sense once a portfolio can be managed as one
  • Multiplies every other feature: alerts, health monitoring, updates, and demo hubs each become N times more valuable when they operate across a whole portfolio
  • A privacy story, not just convenience: scoped roles and clean handoffs replace the credential-sharing workaround with something auditable

Scope

In scope (this roadmap entry)

  • Multi-property account model and property groups
  • Portfolio dashboard with aggregated health and alerts
  • Bulk operations with per-property results
  • Delegated roles and ownership transfer

Out of scope (for now)

  • Billing and invoicing across properties
  • Cross-property scenes and automations
  • Device-level permission granularity for staff

Open questions

  • How fine-grained should staff permissions be: property level, device level, or both?
  • Data isolation: what may a manager see about a home versus its owner, and what stays private to the owner?
  • How does ownership transfer interact with warranties and support contracts?
  • Scale limits: how many properties per account, and what throughput do bulk operations need?
  • Pricing model: per-home pricing inside a portfolio account versus a portfolio tier?

Type to search across

↑↓ navigate ↵ open
⌘K search