Best way for two people to use one budget?

Should both spouses just use one email login? I've used ynab4 for a long time and we shared one dropbox account. 

Didn't know if that's the best way to do both spouses using mobile/online.

Thanks for any thoughts!

107replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • If my husband is logged into our budget through my email will he be able to approve transactions and they update on my phone, also? It would be silly to have to approve everything twice on each persons device 

    Like 1
    • Silver Lightning yes, changes anywhere will propagate to all other devices.

  • I'm concerned that a basic feature as two users accessing a shared budget is not implemented after at least 2 years of people talking about it. I'm coming from YNAB4 and I love the idea of zero-sum budgeting but it seems to me that the R&D department is not at the level I'd be comfortable with. Advising people to share login info is a bad security practice, not only in my opinion. On top of that how the login sharing would work if the account is protected with 2FA? Am I supposed to read numbers to my wife over the phone? I can't help but think that security is not taken seriously.

    Like 2
    • Hi Tan Commander !

      I understand wanting a better method for sharing the budget with your partner and we're working on it!

      In the meantime, if you'd rather not share a password, you can enable Google or Apple login methods in your Account Settings. That would grant your wife access without needing your password or 2FA through your device.

    • Faness Thank you for your time replying to my message, appreciate it! I don't think the workaround is something I'd be using though. My main concern is that you don't seem to take security seriously and were giving bad security advice in the past. That doesn't give me much comfort about how you would deal with my data. That being said, I'll have to go back to YNAB4. Again thanks!

      Like 1
    • Tan Commander We completely understand if YNAB 4 better suits your needs for now! We do take security seriously, it's one of our top priorities, but we understand not feeling safe sharing passwords. I hope you'll consider giving YNAB another chance in the future!

  • When is this feature going to be released?

    Like 1
  • I'll add my name to the list of those who need this feature.  Recommending people share logins as a substitute for multi-user support is very bad security practice that no technology company should ever recommend, and as another user pointed out, this makes using 2FA infeasible.  The only acceptable official responses are "we don't recommend sharing login credentials" or "we're working intensely on this feature and our target release date is X".  Those of you who are chastising those requesting this feature as having trust issues are completely off base and don't understand what's being discussed here.  The fact that you can't imagine a situation where a couple/group/team/family needs this functionality is a testament to either your limited imagination or your overactive opinion.  For a technology company, with a technology product, admin/user role and permission level distinctions is so basic a concept that it's legitimately incredible that the platform has progressed in development this far without it.  If multi-user support costs a premium, fine, I'll pay it - that's not the issue here.  But multiple users sharing the same login information doesn't provide admin/user control, and multiple accounts doesn't allow for shared access to shared information. 

    Like 2
  • Magenta Grizzly Turquoise Projector

    Thank you for sharing your interest and feedback! This feature is definitely a high priority for us.  Our Up Next page is the best spot to keep an eye on for the most up to date details on a timeline, and that page is updated frequently.

    • (formerly Magenta Grizzly): Dela, oh hey friend! Small world! For now my partner and I just made a collaborative Google account for our household, but we'll definitely keep my eye on the release notes for updates on this feature. Thanks for pointing us in the right direction!

    • Daniel Raine Oh, hey!! :) Great to see your face! That's another good solution for the meantime. Sending you and your partner a big hug!

  • Another vote here for a UAC. My spouse and I are trying out google access for now. However if we find a similar service with proper UAC, we're going to switch.

    Like 1
  • I think that is the best way for two people to use one budget.

  • If YNAB wants to keep some customers, they really need to look at competitors (one of which starts with the word 'good') and see that YNAB is behind in best security practices. Please bring multi-account/tenancy to YNAB. YNAB is great if you are single, but my outlook on YNAB is drastically changing as a married man who works in the IT industry with security as a topic of constant focus. Sharing accounts is bad!!

    Like 1
    • Aquamarine Horn Do you have a different lock and key for your spouse to access your house? I agree that giving a copy of your house key to someone else is bad security, but sharing the same house key between the pertinent parties is not bad security. 

      Just to be clear, I can fully see the use of separate logins for different access (children, accountants, even split families, maybe roommates - though that seems very open to mooching on the software). I'm just tired of people making a false analogy with security practices and sharing accounts. 

    • Move Light Sound Life That is a horrible analogy to apply to the digital world. Things in the physical world do not work the same way as in the digital world. With breaches, ransomware, phishing, and malicious actors trying to get information, security is one of the most important elements of design inherent to the fact that the digital world is an imperfect and exploitable creation of our own. It is bad practice and against best security practices for application design to force users to share the same account for a multitude of reasons.

    • Aquamarine Horn 

      Aquamarine Horn said:
      With breaches, ransomware, phishing, and malicious actors trying to get information, security is one of the most important elements of design

       Absolutely. Let's use some logic. 

      If a breach occurs that allows a malicious person into YNAB in general because your spouse is sharing your login, that means your spouse didn't safeguard their credentials and we're all at risk. The onus is actually on YNAB to prevent that type of attack. If a breach occurs that allows your data specifically to be compromised, I'm not sure how having separate logins would fix that problem. The bad actor would still see your data.

      Same thing for ransomware. The security for that should be tight on YNAB's side. If you get some rando holding your specific YNAB data for ransom because your spouse shared their credentials with *not you,* contact YNAB.

      If your spouse doesn't handle phishing well - such that your account is compromised, a separate login wouldn't protect your data, as it's already been compromised. 

      I absolutely expect that YNAB employees have their own work logins that they never share with anyone.  If someone can maliciously attack all of the YNAB data just by being a user, they don't need your spouse's login. They'd create their own. 

      The security issues you listed are important. There are functional reasons to have separate logins. Security of the software is not one of them. 

      If by security, you're trying to set specific access, that is actually security of your data. Let's not conflate the two. 

      Edit: I have feedback that what I'm saying is not conveying what I mean. I apologize, but I'll leave it here as food for thought. Discussion and further education is always welcome in my book. 

      Edit #2-Here's a different set of words:

      "That's normally good security practice, but the things that make it a good practice aren't applicable in this situation."

      Like 1
    • Hi Aquamarine Horn ! If you'd like to share the details of your ideas for sharing YNAB accounts, our product team would love to hear them. You can fill out our Feature Request form.

  • YNAB seems like the perfect budgeting app, but only having support for a single user account feels like a big miss to me. It would be great to see YNAB implement support for 2 users so partners can use their own accounts to sign in via Google that's protected by YubiKey/2FA/MFA.

    Based on how it works today, now I have to lean on my password manager and its abilities to be able to properly secure my YNAB account while having the credentials shared with my partner.

    Like 1
    • Full Piggy Bank Will you share this with our team in a Feature Request? Our design team would appreciate hearing what you're looking for and any pain points you and your partner feel with the current user/account set up.

    • Dela Thank you for sharing how to submit feature requests to your design team, I've gone ahead and done so. Have a fantastic day!

      Like 1
  • I was surprised at all the responses suggesting shared passwords.  I have nothing to hide from my wife, but we just don't share accounts in principle.  Even our shopping list has unique logins.  I will add my voice to the chorus that is requesting multiple SSO logins to the same account.

    If I were to share my google SSO auth with my wife, she would have my google account messing up her phone / PC profiles, or vice versa.  When she logs in, my google 2FA would mean she has to call me to ask me to click "Yes, it was me" as I wouldn't do it normally.

    We typically avoid non-SSO passwords, as they just become something else to manage.  Glad that YNAB supports google SSO, btw.

    So, I am also looking forward to multiple accounts being associated to the one budget account like I already can do with my shopping list :-)  

    Like 1
    • Redlow Thanks for sharing your thoughts on this! Would you be willing to also send them over to our product team as a Feature Request? This way it gets into just the right hands, and they can followup for more details if needed!

  • I really wanted to come back around to YNAB after looking at it three years ago, but I can't for one reason and one reason alone.  Information security, specifically the login fiasco. 

    I work as a DevOps engineer, now, and have held various IT roles, some of which required me to be a key part of internal and external compliance and security audits. 

    Connecting two Google accounts via OAUTH2 is easy peasy. Sure, you'll have to add a flag to your user schema to denote an <account_owner>, but that should have been an MVP kind of feature. 

    Frankly, I'm not willing to risk violating ToS for Google or Apple accounts, and for financial software, I can't accept workarounds. On principle and for all the reasons I preach best IAM practices ( like "one login === one person" ) to my clients, I'm not sharing a login with anyone, even those I trust. 

    I SOOOOOOOOO wanted to use your platform because it really works with how my spouse thinks about money and budgeting. 

    Please, please, please get Identity and Access Management right. I want so very badly to use your product. 



    An Almost Customer, Twice

    Like 1
    • Powder Blue Android In case you haven't seen my pleas to have thoughts like this submitted as a Feature Request, please consider doing so! Every single one is read and gets into the hands of our product team. 

      BTW: would it work for you in the interim to have one of you using the Google/Apple SSO option and the other to use a username/password?

  • Powder Blue Android

    DItto.  Developer / Tech Lead here - we do a lot of work for SMEs, and it's surprising that YNAB are recommending users to share credentials for budget sharing.

    It feels like YNAB sees this issue as one of those features that's "too big" and so it ends up stuck at the bottom of the backlog.

    YNAB - Please fix this - as someone who's worked with integrating green fields new tech and really old (in some cases 20+ year old) systems, I can't think of any sound reason why a company would choose to take this approach, whatever their tech stack, and saying things like "It's too big" or "We can't work out how to get the user subscription billing right" just doesn't cut it in to day's security-conscious world.

    And yes, I'll put this in as a feature request.

    Final thought: I'm willing to bet that if YNAB is moving into the UK Fintech market to support integrating with UK Banks then they'll need FCA authorisation.  Sharing passwords is listed under "Examples of poor practice" on the FCA website:

    P.S. Don't get me wrong, I really love YNAB, it's fantastic!

    Like 2
    • Slate Gray Piranha Thanks for taking the time to submit your thoughts as a feature request! We appreciate all of them. 

      Like 1
      • The Dude
      • Sys & App Admin
      • The_dude_abides
      • 3 mths ago
      • Reported - view

      Marisa , has this Feature Request been added yet? Can you advise how work like this is prioritized and communicated with the external community? Thanks!

    • The Dude Great question! We have a support team dedicated to feedback and feature requests. They make sure every single one makes their way to our product designers, who process the feedback and requests, and in turn, work with our product teams to examine how well something fits within the YNAB Method, and then to prioritize developments. Once a new feature is well on its way, it will appear on our Up Next page. Release notes also show what we're working on. 

      I can confirm that our Product Support Team has definitely received and processed feedback on allowing multiple logins per YNAB account. They love to gather details, though, so if you'd like to add your voice, please do so here.

  • Definitely a critical feature. Login sharing is just not an option. Must have multi-user access. 

    Looks like this has been requested for over 3 years now. Any update on an actual timeline for this feature? 

    The website has this listed as a feature and one of the reasons I signed up. In reality, it might be a feature at some point. 

    Like 1
    • Silver Jackal We don't have a timeline we're able to share at this point, but as Marisa mentioned above, our team has processed many similar requests, and would love to hear from you about the specifics of what you'd like to see!

      At this point, having one partner access the budget via Google or Apple SSO remains the best way to set up multi-user access without sharing credentials! Could that work for you and your partner?

    • Rachel I tried the Google approach, but my wife either has to create a google account on her phone for my email, or she has to use my email and password for login. Unless I am missing something, neither of these is really helpful. If there is some documentation on how she can use her google account and I still use my email, but they go to the same budget, that would be adequate. So far, I have not seen that as an option, or at least not seen how to do that anywhere. 

    • Silver Jackal Thanks for clarifying what you've tried! Your wife should be able to set up Google SSO by logging into her Google Account from Account Settings (no new account required).

      You will need to log in yourself and sit down together to do so. Once set up, she should be able to access YNAB by using "Sign in with Google" from any device, without needing your YNAB credentials or your Google account info. Here's the written documentation, but let us know if you have any more questions about SSO!

Like22 Follow
  • Status Answered
  • 3 mths agoLast active
  • 107Replies
  • 15975Views
  • 65 Following