All Solutions / Connected

Connected / Estalink solutions

Keep your household connected, without confusing access.

Manage Household Member profiles with required contact information and a separate governed App Access approval flow.

Core workflow
PEOPLE IN CONTEXTIllustrative system view
  • Resident context
  • Household profiles
  • Separate App Access
  • Scoped participation
Profiles and access remain separate governed workflows.

Why it matters

Household Management, in context.

Adding someone to a household should not silently give them a login or permissions. Equally, a profile should not have to pass through an obsolete registration-request journey just to be represented correctly. Residents need to see the difference between a person, their profile and an App Access request.

The Estalink approach

A considered way forward.

Estalink keeps direct Household Member profile management active. Phone and email are required in the creation contract. Mobile operation identity uses the reviewed Expo-backed implementation, while backend creation evidence and same-attempt reconciliation protect the intended request from uncertain responses.

App Access remains a separate approval process reached from the Household management surface. Current pending counts represent pending, non-archived own requests within Estate, Resident and requesting-User scope. The existence of a Household profile does not substitute for an approved request or widen access to other Units or Estates.

The workflow

From context to the next step.

  1. Create the profile

    Supply the required Household Member information, including phone and email, in the Resident's legitimate context. Confirm the intended person before submitting.

  2. Resolve the submitted attempt

    The creation flow preserves an immutable attempt and reconciles uncertain outcomes. An interrupted response should not prompt blind creation of a duplicate profile.

  3. Request App Access separately

    Where appropriate, use the existing App Access request from the management screen. Profile creation is not an automatic approval of application access.

  4. Follow the governed outcome

    Review the request's current state and use the permitted cancel/review pathways. Historical registration-request evidence remains retained but is not the active V1 workflow.

Capability focus

What connects here.

  • Direct Household Member profiles
  • Required phone and email
  • Reliable creation/reconciliation
  • Separate App Access requests
  • Own-request pending visibility

Designed for people

Clear responsibilities.

  • Residents managing a household
  • Household Members with approved access
  • Authorized App Access reviewers

Resident Management establishes the host context. Approvals & Verifications explains App Access decisions. Domestic Staff Management uses the related profile foundation with its own category and contact requirements.

Estate AI-OS relationship

Insight without taking authority.

Advisory navigation may help find an incomplete task, but cannot create profiles, approve App Access or disclose another household's information.

Explore Estate AI-OS

Availability & deployment context

Direct profiles and existing App Access requests are core. Retired Household registration-request APIs are not part of the current workflow and are not reintroduced by this marketing page.

Capability availability may vary by estate, deployment and release phase.

A demonstration should establish which workflows are applicable to your Estate, who is authorized to use them and what integration or release conditions still apply. Illustrations on this page are conceptual, not customer records, live metrics or operational controls.

Continue exploring

Connected solutions.

Core workflow

Resident Management

Connect Resident registration, Unit context, profile management and everyday community workflows without crossing Estate boundaries.

Core workflow

Domestic Staff Management

Manage Domestic Staff profiles with required phone contact, scoped credentials and separate App Access requests where applicable.

Core workflow

Approvals & Verifications

Understand permission-scoped registration review, separate App Access approval and current credential verification without blurring authority.

Start with your community

Explore what matters to you.

Discuss Household Management in the context of your people, responsibilities and deployment needs.

Request a Demo