Sign-in and User Identity

Eazo includes user sign-in, session recognition, and identity capabilities, and every new App is ready to use that foundation. When an App needs accounts, personal records, private content, paid-user identity, or payments, the Agent adds an appropriate sign-in interface and isolates each user's data. You do not need to select or register an external authentication service, configure authentication keys, or maintain user sessions.

• In Eazo Mobile: the App normally recognizes the currently signed-in Eazo user without another sign-in;
• In a standalone browser: a signed-out user can use the App's sign-in entry point. Available methods depend on the generated interface.

For a purely public display App, tell the Agent that no sign-in module is needed. Keep sign-in whenever the App stores private data for each user, restricts paid benefits, or accepts payments.