Multi-factor authentication (MFA)

Multi-factor authentication (MFA) adds an extra layer of protection to your Uber for Business accounts, helping to safeguard against unauthorized access and data breaches. This security measure requires users to verify their identity with 2 methods before granting access.

Benefits

• Enhanced security by using 2 methods of verification
• Reduced risk of unauthorized access even if a password is compromised
• Increased confidence in the security of business operations

MFA methods

Once enabled, users will use their password and one of the below verification methods when signing in:

• Passkeys: Use the device’s built-in authentication (fingerprint, face recognition, device PIN, or physical keys)
• Authenticator app OTP (one-time password): Generates a time-sensitive code from an app like Google Authenticator or Duo
  • Requires downloading the app to a mobile device
  • No phone number is attached to the account since codes are generated by the authenticator app
  • Verification codes can be used to sign in via mobile and web
• Recovery phone: Receive a temporary, unique code on your registered mobile device to complete the authentication process

Choosing the best MFA option for account security:

When selecting an MFA method, consider the following options to enhance account security:

• Passkeys

  • Requirements:
    • Users must create a passkey on their device or password manager using the device’s sign-in methods
  • Recommended for:
    • Users with a dedicated device to access the dashboard
    • Users with multiple devices, as passkey can be set up on each device
  • Not ideal when:
    • Multiple users share the same Uber account when the available device sign-in method is fingerprint or face ID

• Third party authenticator apps

  • Requirements:
    • User must download and install a third-party authenticator app, such as Google Authenticator or Duo
    • Available on mobile, desktop, and browser extensions for multiple operating systems
  • Recommended for:
    • Users with a dedicated device for downloading the authenticator app
    • Scenarios where offline access is important, as these apps can generate codes without connectivity
  • Not ideal when:
    • Users don’t have access to the device during sign-in
    • Multiple users share the same account

• [Upcoming] Recovery phone number

  • Requirements:
    • User must provide a recovery/secondary phone number
  • Recommended for:
    • Users who will have access to their phone
  • Not ideal when:
    • Multiple users share the same account
    • Users don’t often have access to their phone when signing in