With 1PW7 and earlier, I could select vaults displayed, which would remain in effect regardless of any tags and/or categories selected. This was very useful and significantly helped reduce clutter and increase efficiency.

With 1PW8 it appears I can no longer do this. I can either select a single vault then have all categories listed, or I can select a category and have all vaults listed. This is inefficient and non-intuitive. I am using categories and tags in the left pane, to be similar to the behavior in 1PW7.

Yes, if I select categories from the dropdown at the top of the item list it will filter on the selected vault. This is even more confusing as the behavior is different depending on how I select categories.

I absolutely hate the new design in 1PW8 and find it much more tedious and difficult to use so I am trying to return to the previous efficient and intuitive usage, unfortunately with great difficulty. It seems the focus was on trying to make 1PW8 \"pretty\" at the expense of efficiency and usability.

1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nBrowser:_ Not Provided

With 1PW7 and earlier, I could select vaults displayed, which would remain in effect regardless of any tags and/or categories selected. This was very useful and significantly helped reduce clutter and increase efficiency.

With 1PW8 it appears I can no longer do this. I can either select a single vault then have all categories listed, or I can select a category and have all vaults listed. This is inefficient and non-intuitive. I am using categories and tags in the left pane, to be similar to the behavior in 1PW7.

Yes, if I select categories from the dropdown at the top of the item list it will filter on the selected vault. This is even more confusing as the behavior is different depending on how I select categories.

I absolutely hate the new design in 1PW8 and find it much more tedious and difficult to use so I am trying to return to the previous efficient and intuitive usage, unfortunately with great difficulty. It seems the focus was on trying to make 1PW8 \"pretty\" at the expense of efficiency and usability.

1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nBrowser:_ Not Provided

@Waterside

I understand your feedback and I've passed it along to the product team. Thank you for sharing your experience with 1Password so that we can make the app easier and more intuitive to use in the future.

-Dave

(sigh)

Sadly the point is still being missed, and sadly this seems to be the general theme with 1PW8.

If the reasoning earlier was that the new method is more intuitive than the old method, I would submit that this new behavior is far less intuitive.

Yes I am very aware I can disable the categories in the left pane. I intentionally want to be able to select categories from the left pane as had always been the case with 1PW previously. You have now completely broken this behavior and in response are even suggesting this functionality not be used at all?

To your point about scope: I can certainly combine \"scopes\" (as it appears) by simply choosing categories from a different place. This makes absolutely no sense. While you may know the internal workings of your product, you should not expect your end users to know similarly. Another way to look at it: How should your end users know that when selecting a category at the top of the item list that it is a filter, but when selecting a category in the left pane it is a scope? This is nothing more than meaningless and confusing semantics that only frustrate your users.

Please read this again (really - please actually READ it): With 1PW7 and previous we had categories in the left pane, and selecting these would filter from only the vaults selected. You have now completely broken this behavior. To make it worse you offer two places to select categories and the two behave completely different? Do you not see how confusing, unintuitive, and unproductive that is?

This is very sad. To be honest 1PW8 is a disaster, and judging from so many threads in these forums I am not alone in this thinking. Both new and previous users are complaining about the same lost functionality over and over, across all platforms, and none of it has been returned. Instead we only get excuses. It is like there is an entirely new company that took over with an entirely new product for 1PW8 that completely ignored everything that made 1PW7 and earlier such great a great solution.

@Waterside

1Password 8's sidebar allows you to \"scope\" the items that you see according to a certain selection such as a vault, tag, or category. You can't select more than one of these scopes as you can only select one option at a time from the sidebar.

At the top of the centre column are sorting options that allow you to filter and organize what you already see in the centre column. So if you have a certain vault or tag selected in the sidebar you can further filter that list according to a specific category. Categories in the sidebar are disabled by default and, if it makes things less confusing, you can disable them again so that you only see the Categories menu above the centre column:

\n
1. Open and unlock 1Password for Mac.
\n
2. Click on 1Password next to the  in the menu bar.
\n
3. Click on Settings.
\n
4. Click on Appearance.
\n
5. Turn off \"Categories\".
\n

That being said, I understand your feedback and I've forwarded your comments to the team. 🙂

-Dave

I appreciate the suggestions but this still misses the point.

This is a significant change in behavior, and this change is also not consistent across the various implementations of 1PW8. For instance the standalone browser app does not support collections - whether or not this is to be addressed is not relevant. For now this makes 1PW8 painful to use and much less intuitive than 1PW8.

This also does not address the point about the inconsistency within 1PW8 desktop itself. IF I select a category using one method the filter is applied to just the vault I have selected (the expected and desired behavior). If I select a category using a different method in the very same app I get completely different behavior and the filter selects and applies to all vaults. This is broken, IMHO.

I didn't find the previous functionality all that unintuitive. I do find that the new implementation of collections is more confusing and unintuitive however. I don't understand why the old behavior was removed.

Really - this is horrible. Once again I would ask that you stop forcing your customers to do something the only way you want it to be done. Adding features is not he issue, removing existing features and functionality simply because you think we should do something different is the issue.

FWIW this topic is related/similar to several others in this forum from other users that are getting surprised and confused by this also, and the lack of consistent behavior anywhere within 1PW8 is only making this worse.

@Waterside

Thank you again for sharing your feedback, as a long-time user we're always interested in hearing from you since your experience with 1Password helps us understand how we can further improve it for your needs.

As you're likely aware, 1Password 7 included a view called \"All Vaults\" that users could modify to only include certain vaults and not others. In my opinion this wasn't intuitive at all and, over the years, I've spoken to countless users who were confused about what this option was or why we called it \"All Vaults\" when in reality it was a user-selected collection of vaults.

Collections in 1Password 8 solve the problem by getting rid of the confusing \"All Vaults\" function and instead allow folks to create their own group of vaults, or even multiple groups of vaults. A collection allows you to organize your items into dedicated vaults for different purposes and then group them together to only see the vaults that you need at a particular time or for a particular task.

For example, you can have a collection that only includes your work vaults and another collection that only includes your personal vaults. With 1Password 7 there was no easy way to switch between these two different groups of vaults, 1Password 8 gives users that functionality right from the sidebar. And 1Password 8 remembers which collection you had open last and will automatically select that collection the next time that you use the app.

And, if you wish, you can create a collection that only contains one vault if there aren't any other vaults that you'd like to include.

That being said, our developers are not done with 1Password 8 and they're working hard on further improvements and refinements. I've passed along your feedback that you'd like to see closer integration between 1Password for Mac and 1Password in the browser when it comes to selecting, and using, collections/vaults to the team. 🙂

-Dave

ref: PB-31433631

This just highlights that the browser standalone app and desktop standalone app are now disjoint and not consistent, which is my point in the browser thread.

Again I appreciate the suggestions but it is largely missing the point about usability and efficiency. With 1PW7 and before I would select one vault in the desktop app (or mini), and that was honored and used everywhere. Now I need to repeat my choices differently depending on how I am using 1PW. I used to be able to quickly and easily select a vault and use that selection everywhere but this has been thrown out the window.

You can optionally set a vault from with 1Password in the browser. Right-click on the toolbar icon and select settings. From there in the accounts section you can remove vaults from view/use.

I still think you are missing my point. I appreciate the suggestions for possible alternatives.

The difference noted here between the browser and desktop app is yet another reason why I dislike 1PW8 and have growing disappointment with the direction of this solution (1PW). When these had an integrated option (that actually worked) suggestions like this would have been more helpful. Instead this completely ignored the fact that I may want to use 1PW with a browser, and that I would like consistent behavior between desktop and browser. Please recognize this.

From a different perspective:

I have created multiple vaults since I intentionally want those items separate. The reason is irrelevant. The fact that I went through the effort to separate them is all that is needed, and previous to 1PW8 this was honored and supported by 1PW. Now with 1PW8 my desire to keep those separate has been completely cast aside and AgileBits has decided instead to munge them all together and instead suggest multiple different options for multiple different purposes as workarounds.

Adding collections may be great. Completely discarding previous functionality, ignoring your user wants/needs, then forcing them to use a new option is just really bad. On top of it that alternate option is neither complete nor does it necessarily meet all the needs of having separate vaults.

To make it clear: I don't want collections forced on me to keep my intended separation in vaults. I want the original behavior maintained where separate vaults are, well, separate. I can use collections if desired for additional functionality but should not be forced to.

Correct on the browser portion. This was posted in the Mac section. The two are companion apps. My recommendation would be to look at Quick Access. Which can use a collection. It can get confusing. I really hope we can see this in the browsers soon. I know I would love it, hands down. I'd be glad to ping the team and let them know this matters to you. This is one of the reasons I rely on Quick Access a lot now.

As you've noted yourself in another thread, collections don't work with the browser extension.

Collections also don't address the difference in behavior I noted. If I select a category in one place, it applies to all vaults (why???). But if I select a category in a different place it only applies to the vault I have selected.

The latter matches the previous behavior which is expected. These are the types of changes that hinder efficiency and usability, and seeing other threads report similar types of issues shows I am not the only one that feels this way. Why go out of your way to break existing functionality?

Across my feedback there is a consistent theme: 1PW8 makes a major step backwards in usability and efficiency. So many features and functionalities have been removed that it 1PW8 is now cumbersome to use. I keep coming back to these forums to find alternate methods and keep seeing that something either is no no longer available, or the alternate is only a partial workaround.

I originally chose 1PW long ago (v3) since it was secure, lightweight, and easy to use. Two of those no longer apply to 1PW8, and the book is still open on the other.