CHYPHNX / IDENTITY & ACCESS

Deployment staged · Sign-in not active yet

ONE FRONT DOOR.
EVERY ACCOUNT IN REACH.

Sign in to CPX with one passkey. Select any connected Google or Microsoft identity. Launch Proton, Samsung and other accounts using secure autofill—without giving up their native safeguards.

This is the public onboarding overview. Do not enter passwords, recovery codes, or authorization tokens here.

YOUR ACCOUNT HUB DESIGN PREVIEW
CHYPHNX IDPasskey first · Scoped access
GGoogleMultiple profiles
MMicrosoftSchool + personal
PProtonVault autofill
SSamsungNative account
Account choice ≠ automatic permission. Every provider remains in control.
Simple by default

CONNECT ONCE.
KEEP CONTROL.

01

Unlock your CPX identity

Use your phone, fingerprint or hardware passkey. No new shared password across providers.

02

Choose the exact account

Link each Gmail or Microsoft identity separately, using the provider's own OAuth consent screen.

03

Launch securely

Switch accounts from one dashboard. Use your encrypted password manager where OAuth SSO is unavailable.

Connection models

EVERY PROVIDER.
THE RIGHT METHOD.

GGoogle / GmailMultiple Google accountsOAuth

Each Google account has its own verified identity and consent. Signing in does not automatically grant access to Gmail messages. Google may request additional verification.

MMicrosoft / Student IDPersonal, OneDrive and university tenantsOAuth

Work/school and personal accounts remain separate. Your university may require IT approval or its own MFA. Samsung-linked OneDrive remains a Microsoft connection.

PProton Mail / DriveMultiple Proton accountsVault

Use native Proton account switching and encrypted autofill. Proton personal mail does not accept arbitrary CHYPHNX SSO in place of Proton authentication.

SSamsung / Other appsDevices, services and legacy websitesAutofill

Use provider-specific passkeys when available or unique passwords in an audited encrypted vault. Preserve device recovery and original account MFA.

Continuity by design

NO MORE SINGLE
POINT OF FAILURE.

01 / RECOVERY

Two independent passkeys

Primary phone plus a spare hardware security key. Store emergency admin recovery separately.

02 / DATA

Encrypted, tested backups

Back up the identity database, keys and configuration offline and offsite. Verify an actual restore before cutover.

03 / AVAILABILITY

Independent emergency access

Retain provider-native login and a break-glass admin path if your SSO service or phone goes offline.

Identity service readiness

Infrastructure source and integration policies are staged. The identity host, TLS, provider OAuth clients, enrolled passkeys and tested recovery remain pending.

NOT LIVE