Skip to content
kumo

Sign-in Security

kumo can ask for a second step each time you sign in, on top of your emailed sign-in link, Google, GitHub or your company’s sign-in. It is off until you, your studio or one of your projects turns it on.

  • A passkey. Your device checks your face, finger or PIN: Face ID or Touch ID on a Mac, iPhone or iPad, Windows Hello on a PC, the fingerprint or face unlock of an Android phone, or a security key such as a YubiKey. The key that signs you in never leaves the device. A passkey saved to iCloud Keychain, Google Password Manager or a password manager works on your other devices too.
  • An authenticator app. Google Authenticator, Microsoft Authenticator, 1Password, Authy or any app that shows six-digit codes. Each code works once.
  • Recovery codes. Ten one-time codes you get when you set up your first step. Keep them in a password manager: each one signs you in once if your passkey and phone are both out of reach.

Open the account menu (your name, bottom left) and choose Sign-in security. The page opens in your browser, where you signed in to kumo. There you can:

  • add or remove passkeys,
  • set up or remove an authenticator app,
  • make a new set of recovery codes (the old set stops working),
  • turn Two-step sign-in on or off for your account.

If your account already has a second step, the page asks for it before it shows or changes anything.

In Settings → Team, the Two-step sign-in section has a switch for Everybody in the studio (studio administrators) and one for the members of each project (its owners, and the studio’s administrators).

  • Anyone it applies to is asked for their second step at their next sign-in. Somebody who has none yet sets one up there, in about a minute.
  • Apps already signed in without a second step lose access to that studio until the person signs in again with it, so turning it on takes effect at once, not when old sign-ins expire.
  • Turning it off stops asking; people keep the passkeys and apps they set up.

For a passkey, its public key, when it was added and last used, and nothing about the device: no name, no model, no biometric data. Your face or finger is checked by your device; kumo only learns that the check passed. An authenticator app’s secret is stored encrypted, and recovery codes only as one-way digests. See the privacy policy for the full list.