One Front Door, Many Independent Apps

A front door you can read at a glance

A growing collection of applications should not require a growing collection of remembered URLs. Polinaria Home gathers the destinations into one catalog. Each card says where you stand: available, requestable, pending, declined, synchronizing, or coming soon.

Concept illustration for polinaria-home; not a product screenshot.

A front door for the trusted pilot

The same surface supports the platform's small trusted pilot. A visitor can request a Polinaria account, while an approved member can sign in, see the applications relevant to them, request additional access, and launch confirmed products. The experience stays intentionally legible: Home describes the application and its availability without exposing the internal role or identity machinery behind it.

From discovery to a confirmed destination

This is the successful access path. A pending or declined request remains visible as such.

flowchart TD
    Catalog[Browse the catalog] --> Request[Request application access]
    Request --> Review[Administrator review]
    Review --> Confirm[Identity plane confirms access]
    Confirm --> Launch[Launch the application]

Shared identity without hidden authority

Home also gives each member a small shared profile with a display name and avatar. That identity makes the platform feel coherent, but it does not erase the applications' independence. Every destination owns its own session and its own in-product permissions, so the launcher remains a guide rather than becoming a universal administrator.

For platform administrators, Home includes a dedicated workspace for reviewing pilot requests, confirming application access, controlling catalog visibility, and seeing whether downstream access changes actually succeeded. It turns a potentially fragmented onboarding process into a single, understandable journey for both the person joining and the person responsible for helping them in.