01
eFind ONE
Identity: who is signed in, what account they use and which services they can access.
Identity + account
eFind ONE
One account, one identity layer and one place to authenticate across the eFind ecosystem.
LIVE
The quiet layer
The best identity system is the one you barely have to think about.
Every ecosystem eventually meets the same wonderfully glamorous question: who is signed in?
eFind ONE is the centralized identity, account and single-sign-on service across eFind. It is the layer that lets a person use one eFind account across participating products rather than building a separate identity in every corner of the company.
ONE is not a separate consumer app competing for attention. It is infrastructure for the relationship: authentication, account access and the permissions that let products know who is using them.
One login is useful. One enormous undifferentiated bucket of data would be rather less clever.
eFind ONE
ONE
SearchMailAdsDrive
What ONE is for
Identity without making identity the product.
The account layer should make the ecosystem simpler while preserving clear boundaries between services.
ACCOUNT
One eFind account
Create and use a central account across participating eFind services.
SIGN-IN
Single sign-on
Authenticate once and move among supported eFind products without a collection of unrelated credentials.
PERMISSIONS
Boundaries matter
Identity can connect services without implying that every product may read every piece of information.
FUTURE
A foundation for devices + services
A consistent identity layer becomes increasingly important as eFind expands across software, devices and business services.
A simple model
Who you are is not the same thing as what you know.
02
eIntelligence
Intelligence: the shared reasoning and assistance layer.
03
eDrive
Personal context: files, photos and memories a person chooses to store or connect.
04
Products
Capabilities: Search, Maps, Mail, News, Weather, video, advertising and whatever comes next.
The principle
Connection without collapse.
A unified ecosystem should feel coherent to the person using it. That does not mean every service should become the same service or every dataset should be combined by default. ONE exists to make the relationship simpler—not to erase useful boundaries.
What ONE should prevent
One account should remove duplication—not erase boundaries.
The easiest way to build an ecosystem badly is to confuse “connected” with “combined.” A person may want the same account for Mail and Maps without wanting every service to know everything the other service knows.
AUTHENTICATION
Prove the account once
ONE provides a common authentication relationship so participating services do not need to invent separate account systems and separate recovery experiences.
PERMISSIONS
Make access explicit
Connection between services should depend on permissions that can be understood, changed and revoked. Identity is the doorway; it is not a universal key left under the mat.
RECOVERY
Treat account recovery as part of security
A centralized identity layer is only useful if recovery, device changes and suspicious access are handled carefully. Convenience and security have to be designed together.
EXPANSION
Be boring enough to scale
As eFind adds services and, eventually, devices, ONE should make the relationship more consistent without becoming another destination people have to visit every day.
Identity layer
One account should reduce friction, not create a data free-for-all.
eFind ONE is the centralized identity, account and single-sign-on layer across participating eFind services. It answers a fairly boring but important question: who are you, and what are you allowed to access?
Authentication is not intelligence
ONE signs a person in and manages the account relationship. eIntelligence handles intelligent experiences. Keeping those concepts separate makes the architecture easier to reason about—and easier to explain.
Identity is not permission to combine everything
A shared login should not automatically mean every service gets every piece of information. Product permissions still need to describe what is being connected and why.
The best SSO is mostly invisible
People should not have to learn the org chart to move between eFind products. Sign in once, see what you are connected to, and keep controls understandable.