nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Remember me

Saunders-Nazareth

Each time I logon to a Quicken site, I have to login again. That means entering username, password, and then a code sent to a device or email. Here is an idea… remember me on a trusted device. Store a token in the browser. I signed in five times in the past 10 minutes. That is a terrible user experience.

Find more posts tagged with

Reviewed

Status: Reviewed

Comments

Quicken Anja

Hello @Saunders-Nazareth,

Thank you for taking the time to reach out with your request and for sharing your feedback!

I went ahead and changed your post to an Idea so other users who have the same or a similar request can vote on your idea by clicking the up arrow (see below).

Thank you!

jacobs

@Saunders-Nazareth For the Quicken Community forum (this site), it already DOES remember you. For me, I'm remembered and remain logged in all the time, and once or twice a year when the cookie/token expires, I get asked to log back in.

Additionally, can't you save your login info in your browser? I'm on a Mac, so perhaps it's different on Windows, but it takes me one tap on my finger ID (or no tap on a Face ID device) to login to most websites.

Chris_QPW

@Saunders-Nazareth you need to specify which site you are talking about.

If it is this site, then I agree with @jacobs I almost never have to login.

For the Quicken.com account site I do need to log in with my username and password every time.

What I don't understand is the statement about the code. It requires me to login with my username and password, but it doesn't send a code each time, that is "cached" in my web browser (MS Edge).

I use a password manager so filling in the username and password is easy, and I think given the sensitive information on that site one should be required to log in each time.

I suspect that @Saunders-Nazareth is dealing with a web browser problem.