Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
Solved
A separate Favorite list for each family member
I noticed that in the past others have asked for the ability to create a separate favorites list for each family. Is there any information about 1Password's current view on this request or estimated implementation date?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Hello astandre! 👋
Thank you for reaching out! Changing favourites to be per-user rather than per-item is a request that is in our product team's backlog but there are prerequisites that have to be developed first before the team can consider making the change. Each item is responsible for declaring whether it is a favourite or not, this system was developed in a time when sharing items in 1Password wasn't as common as it is now. Before favourites can be made per-user this per-item metadata has to be moved out of the item and into a new user-specific layer in the database. Creating this user-specific layer requires some architecture work and, for the moment, this work is yet to be done.
That being said, I've added your comment to the open feature request for this change. Hopefully this is something that can be done in the future.
-Dave
ref: PB-45434265
24 Replies
Hi,
I subscribe to the family plan, and it would be nicer (for me) if when I looked at my favorites I only saw mine, not my wife or kids.
These are for our shared items in common vaults.
I have several vaults:
Myself
Myself + wife
Myself + wife + kid1
Myself + wife + kid2
Myself + wife + kid1 + kid2
It's those shared accounts (mostly with the kids). It's nice they can favorite their stuff, but I would rather not see it. I realize I might be using this unconventionally, but I have been a 1PW user for 15+ years, and my kids were infants when I first started some of their accounts.
Can I make a feature request that would set the favorite for the vault on a per user basis ?
So Kid1 can favorite web site x in the vault "Myself + wife + kid1", but it's not one of my favorites.
Anyone else use 1PW this way ?
I realize I could split apart all their stuff in their personal Kid1 vault, but when they call home and need help with web site x or whatever, it's nice that I can log in from my local machine and help out.
~Scott
I use 1PW the same way as Scott. I was shocked to learn tonight that favorites are family based. The entire concept of favorite suggests personal. This seems more like a bug than a feature request.
Chris
- 1P_Dave
Moderator
Thank you for the feedback. At the moment, whether an item is a favorite or not is metadata that is stored in the item itself. So if one person makes an item a favorite then the item becomes a favorite for everyone who has access to that item.
Changing how this works would require deeper architectural changes in how 1Password works, storing item metadata separately from the item itself, and it's something that the team would like to look into in the future but I don't have any firms plans or timelines to share at the moment.
-Dave
PB-50588239
Thank you, this would be useful to my family, and it sounds like others as well
- 1P_Dave
Thank you again for the feedback!
-Dave
Thanks for the information. This feature will be very useful to us when it becomes available
- 1P_Dave
Hello astandre! 👋
Thank you for reaching out! Changing favourites to be per-user rather than per-item is a request that is in our product team's backlog but there are prerequisites that have to be developed first before the team can consider making the change. Each item is responsible for declaring whether it is a favourite or not, this system was developed in a time when sharing items in 1Password wasn't as common as it is now. Before favourites can be made per-user this per-item metadata has to be moved out of the item and into a new user-specific layer in the database. Creating this user-specific layer requires some architecture work and, for the moment, this work is yet to be done.
That being said, I've added your comment to the open feature request for this change. Hopefully this is something that can be done in the future.
-Dave
ref: PB-45434265
Hey DT,
Great to hear from one of the Originals. As a long time user from back nearly 20 years, nice to see you are still involved. Thanks for working to address this issue.
~Scott
Please add us (tapconet.com) to your list of people needing this fix. In a large, mixed, team, the lack of scope control for Favorites severely limits their utility. And since Favorites automatically rise to the top when using the browser extensions, they just get in the way. We fear users will try to use other password manager solutions rather than 1Password, and we'll lose the centralized management & control we have.
We see reddit responses from your staff, dating back at least two years, which basically echo what you've said here, "The favourite status is currently baked into the item data, which coincidentally makes it more difficult to change..." This really needs to move up the To Do list.
-nic
- 1P_Tommy
Thanks Nic,
I've shared your message internally.
PB-47209564
Since it feels like all discussions on this topic have been closed in the past 6 years (without any plausible, comprehensible explanation), I'm opening a new one.
Problem:
Favourites are organisation-related and not user-related. This makes absolutely no sense, as HR or Marketing, for example, have completely different favourites than, for example, Technicians or the SOC.Solution:
Implement favourites at user level instead of organisation levelor let me put it another way: .... you don't have to eat pizza hawaii just because it's your flatmate's favourite pizza, do you?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not ProvidedStill no news about such a "basic" point?
- 1P_Dave
Thanks for following up! I’ve merged your thread with another discussing the same feature request.
While it may seem simple on the surface, implementing this would require changes to how item metadata is structured and stored, a larger undertaking that hasn’t been prioritized yet. You can find more details in this reply.
-Dave
No News regarding that?
- 1P_Tommy
Sorry, no, not at this time.
