Hey folks - there are a couple of items going on in this thread:
- Share/“un-share” UI/UX. There is a request to make sharing via collections more point+click and less visually confusing, as well as making it easier to manage who has access to what data. This is good feedback, and we are always looking to make things as easy for end users as possible, within the scope of security and our architecture’s purpose.
We handle sharing the way we do currently (from a UI/UX standpoint) with a leaning towards enterprise-group-usage moreso than many individual user-user shares
- Request to actually “un-share” data. This is where it gets tricky and opinionated. Data can’t be truly unshared, as @d.b described - and the best practice is to remove the credentials & change them.
In regard to product functions, the guise of “un-sharing” can be had by doing one of 2 things:
- The org admin / owner can clone the item and delete the shared item
- The item in question can simply be unassigned from any collections, or to a collection available only to a specific user-group (perhaps one that handles password changes?)
Hopefully this answers more questions than it creates