Vault Permissions is not displaying the cog wheel

@bwoodruff Thanks for this detailed post & your general on-going patient and very clear answers. And, if you're collecting customer votes I'd love to see a Read Only feature for Families. I'm up and running already after using 1P for years and this would just be a perfect feature for me.

I'm with @SKreisberg on this one as well, and to be honest I was surprised that even "read only" wasn't an option, considering that the launch email from @dteare listed What if I share passwords with my family and they delete them by accident? as one of the use cases, which clearly isn't possible in Families right now.

That said, I can't see the need for completely fine-grained permission control in a "Families" environment, so I think it's totally fair if they want to keep Teams more advanced to distinguish it (and, frankly, to keep things simple for typical "Family" type users). Personally, I think basic Read and Read/Write would do for most use cases, with "Export" and "Manage" being automatically granted to Owners, but not really necessary for anybody else. I guess one could argue that variations on "Export" could come along with Read and Read/Write, but I guess that's more open to debate.

Ironically, the problem right now is that Owners appear to get Read/Write/Manage on the Shared vault, but not Export, unless they're specifically added by another Admin, which in turn grants them "Full Access."

Ultimately, I think the whole process of simplifying the permissions in Families has actually created a bit of a mess right now, so I look forward to seeing this get simplified. I guess AgileBits can't exactly start with the granular controls and then later take them away, but if that was going to be the case, the permission structures should have been better-defined before Families was rolled out.

I think some level of permission control is a must, also for families.

One might want to set up a shared vault with limited write access so family members can create new items but can't delete anything. Even better would be that members could read/write/delete their own items in a shared vault, but only read items created by other members.

At the very least, simple read-only vaults should be possible IMO.

Frank

Can I create a shared vault but NOT have ALL family members see it? I'm not seeing a way to do that.

We REALLY do need the ability to restrict specific family members from a vault. It can be an all or nothing thing if needed. I just want to have a shared vault for my wife and I and NOT allow my mother (who lives with us) to see/share/use that vault.

I can fully understand the need to offer two tiers of complexity/pricing. But I must say that a read-only capability is the most obvious requirement for a family account.
I am trying to educate my daughters of the wonderful resource that the web can be, hand-in-hand with the fundamental security know-how that web users must understand. I have set them up with their own vaults and want them to take some level of responsibility for managing their increasing presence on the web. That being said, I would hate for them to accidentally delete or modify something and lose confidence in using the internet as a repercussion. A read-only capability would prevent that scenario and was the first feature I would anticipate in a Family orientated offering.

This kind of leads me into a related question... now that our vaults are "online", what is the best backup strategy for vaults? I use Time Machine and Carbon Copy Cloner and also Backblaze online backup, but I am not sure where local copies/caches of the vaults reside on my local disk (if anywhere).

I would not expect Agile Bits to provide guaranteed backup (else I am sure you would have touted it as a feature of Teams/Families), but for my own peace of mind I would like to understand a little more about this aspect of data management.

Thanks for a great product, but please implement the read-only feature ASAP!