Confirm it’s you for sensitive actions
Some actions are risky enough that Syntic asks you to prove it’s really you again, even though you’re already signed in. If you use two-step verification, these actions only work from a session that has passed the code check.
Actions that ask for an extra check
| Action | What Syntic asks for |
|---|---|
| Creating an API key | A session verified with your second factor, when you use two-step verification or your organization requires it |
| Regenerating recovery codes | A fresh code from your authenticator app |
| Deleting your account | A sign-in within the last 15 minutes, plus your second factor if you use two-step verification |
| Sign out everywhere | Your second-factor code first, if you use two-step verification |
| Changes requested by Syntic Code or Syntic Desktop | A recent sign-in on the Confirm it’s you page |
Some billing and team changes also require a verified session.
Messages you may see
- “Deleting your account requires two-factor verification. Verify your second factor and retry.”
- “For your security, sign out and sign back in, then delete your account within 15 minutes.”
- “Enter your two-step verification code first, then try again.”
In each case, sign out, sign back in (completing the code step), and repeat the action.
The Confirm it’s you page
When Syntic Code or Syntic Desktop needs to make a sensitive change to your account, your browser opens a Confirm it’s you page saying which app asked. Choose Sign in again, complete the sign-in, then Confirm under “Confirm this change?”. You’ll see “Confirmed.” and can return to the app. Choose Cancel if you didn’t start this.
The page needs a sign-in from the last 5 minutes, so it may ask you to sign in even if you were already signed in.
Why this exists
If someone steals a browser session (for example from a shared computer), these checks stop them from creating keys that spend your money or locking you out of your account.