Confirming it's you
Which actions ask you to prove who you are before they open new access to your account, how you prove it, and how long a confirmation lasts.
Some actions give someone a lasting way into your account: a new API key, an app you connect, a device you sign in, a person you invite. Being signed in is not enough for these. Symbol asks you to confirm it's you first, so someone who gets hold of a signed-in browser cannot use it to create their own way in.
How you confirm
Symbol asks for the strongest proof your account has:
- Authenticator app or a backup code, if you use two-step sign-in.
- Your password, if you do not use two-step sign-in.
- A code emailed to you, if you sign in only with Google. Anyone who can read your mailbox can also read that code, so keep your email account secure.
If your account has a passkey and your browser can use it, the prompt for the actions that remember for 10 minutes also offers Use a passkey instead. The one exception is signing in to the Symbol app through your browser, which asks for your usual proof. The actions that ask every time never take a passkey.
A wrong answer counts against the same limit as signing in, so confirming gives no one extra guesses at your password.
Actions that ask, then remember for 10 minutes
After you confirm once, Symbol does not ask again in that browser session for 10 minutes. The 10 minutes start when you confirm and are never extended. Signing in with your password, completing two-step sign-in, or signing in with a passkey counts as confirming. Signing in with Google does not.
- Creating or rotating an API key, personal or for an organization.
- Approving an API key request from the terminal.
- Allowing an app to connect to your account.
- Approving a terminal sign-in (
symbol login). - Signing in to the Symbol app through your browser.
- Inviting someone to an organization, resending an invitation, or changing a member's role.
- Removing a passkey.
- Turning Sentinel on or off, changing its rules, or overriding its decision.
The confirmation belongs to that one browser session. Another browser, another device or another person cannot use it. Changing your password or two-step sign-in, or signing that session out, ends it at once.
API keys, apps and assistants can never confirm on your behalf. A key cannot create another key: the CLI asks you to approve a key request in your browser instead (see the CLI).
Actions that ask every time
These ask for proof in the same step, every time, even if you confirmed a minute ago:
- Setting up your first authenticator app.
- Adding a passkey.
- Deleting your account.
If you cancel, nothing happens: no key is created and nothing is approved. Invitations you added while setting up a new organization are kept, so you can send them after you confirm.