Emiko Login And Identity

Emiko uses one identity model across the ecosystem. A user can sign in once, but the visible scope still depends on granted access and assigned permissions.

Emiko App

Emiko App is the customer-facing access surface across web, iOS, and Android. It is where outside users enter the ecosystem, request access, and use services and equipment available to them.

Customer login to Emiko App

Emiko Console

Emiko Console is used by Partners and Resellers for administration. Partners use it to manage their own Emiko Organization, Emiko Sites, equipment, user access, and local operational relationships. Resellers use it with extended permissions to create Partner Organizations and Emiko Sites.

Partner login to Emiko Console

Supported Sign-In Methods

Emiko currently supports these sign-in methods.

The documented sign-in model currently includes Google, Microsoft, and email sign-in.

Access Scope

Authentication and access scope are not the same. A user can sign in successfully and still only see the roles, partner relationships, and permissions that have been granted.

Email Sign-In And MFA

When email sign-in is used, the flow includes email-based verification and MFA / 2FA.

Identity Is Shared, Access Is Not

One login does not mean one unrestricted view. A user can authenticate once and still have different scopes across the ecosystem depending on role, partner relationship, and granted access.

What Comes Next

The next step is to explain how Emiko equipment connects to the platform and how equipment can be understood as independent connected units in the shared ecosystem model.


Public revision 21/05/2026