Skip to main content

Trusting a new device

Learn how to trust a new device to avoid entering two-factor authentication codes when logging in.

Written by Rodrigo

If you have 2FA enabled for your account, you’ll be asked to enter a verification code the first time you sign in from a new device.

If you don’t want to enter a verification code every time you sign in to your Podia account, you can choose to trust the device you’re using.

You can trust up to 5 devices. Once a device is trusted, you won’t need to enter a verification code the next time you sign in from that device.

This is useful if you access your Podia account from multiple devices while keeping 2FA enabled.

Trusting a new device

Trusting your device is simple and can be done when logging in for the first time on a new device.

To trust a new device, simply check the box “Trust this device to avoid further verification”.

Please note: if you are using a private browser,VPN, or private relay on a mobile phone, we treat these login attempts as if they are coming from unique devices.

You can check all of your trusted devices directly from your Account settings.

FAQs

Why should I trust a device?

If you have 2FA enabled for your account, you’ll be asked to enter a verification code the first time you sign in from a new device.

To avoid entering a verification code every time you sign in to your Podia account, you can choose to trust the device you’re using.

Make sure you only trust personal devices and always avoid trusting devices that are public or shared by multiple users.

For how long is a device trusted?

Each login session will expire after 30 days. You must complete the same process again after 30 days and trust your device again.

How many sessions can I trust at the same time?

You may have up to 5 login sessions verified at any given time, each of which expires after 30 days. Logging into a 6th session will log out the oldest session.

Can I remove a trusted device?

Yes. You do it by removing the associated session on Podia and clearing your browser's cookies.

Did this answer your question?