<div dir="auto"><div><div dir="auto">How important are these services if they are not continued and what would the impact be if they weren't? If they are critical then probably best to get them managed by an organisation, incorporate or entity (or partner) that is made up of a team, so that knowledge and access to the systems to maintain them is well documented throughout that team or partnership.</div><div dir="auto"><br></div><div dir="auto">That entity could be made up of entirely one person but that brings risk as you are no doubt aware of.</div><div dir="auto"><br></div>I hate to say this but once your dead all those are no longer really your problem. If a customer is concerned about that risk, then they might choose to outsource the managed services elsewhere or with an entity that has redundancy in its personel.<div dir="auto"><br></div><div dir="auto">Benjamin's idea of deadman switch is in bitwarden is good, but that may be a paid feature, you would still need a level of documentation to hand over to any successor, so I guess that brings with it a kind of chicken and egg scenario. How do they securely access the documentation?</div><div dir="auto"><br></div><div dir="auto">Seems like there isn't much demand for a cost-effective solution to this sort of problem but a way to mitigate it might be to decouple any service accounts from personal email addresses and credit cards etc. So that account recovery and liability to next of kin is reduced.</div><div dir="auto"><br></div><div dir="auto">You might even want to engage with lawyers and or other professionals especially on minimising liability aspect. That would be my main concern to not drag family members into potential financial debt carried forward from such an unfortunate event (death).</div><div dir="auto"><br></div><div dir="auto">I guess that's why things like trusts require at least two directors to operate...</div><div dir="auto"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 28 Apr 2021, 13:38 Benjamin, <<a href="mailto:zorlin@gmail.com">zorlin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Mostly something like BitWarden with a password distributed by a dead man's switch. Or you could use Shamir's Secret Sharing and give keys to your wife, lawyer, friend, dog etc.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 28 Apr 2021, 13:36 Onno Benschop, <<a href="mailto:onno@itmaze.com.au" target="_blank" rel="noreferrer">onno@itmaze.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Over the past few years I've been attempting to resolve a problem that is only getting larger. I have countless online accounts, some of which are paid for and linked to credit cards and bank accounts.</div><div><br></div><div>These accounts are not just "end user" accounts, but things like a domain account, the hosting for a fleet of websites, online photo storage, backups, client data and resources, email, calendaring, media, streaming, etc.</div><div><br></div><div>What systems have you put in place to ensure continuity?</div><div><br></div><div>Note that this goes well beyond password sharing, a whole topic in and of itself, this is about how stuff is linked together, what belongs to which account, how is it paid for, etc. etc.</div><div><br></div><div>I note that even if I were to document this accurately, it would be out of date almost immediately. I created three new accounts for services in the past three hours alone.</div><div><br></div><div>Feedback and discussion welcome.<br></div><div>-- <br><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr">Onno Benschop<br><br>()/)/)() ..ASCII for Onno..<br>|>>? ..EBCDIC for Onno..<br>--- -. -. --- ..Morse for Onno..<br><br><span style="color:rgb(136,136,136)">If you need to know: "What computer should I buy?" </span><a href="http://goo.gl/spsb66" style="color:rgb(17,85,204)" rel="noreferrer noreferrer" target="_blank">http://goo.gl/spsb66</a><div><br>ITmaze - ABN: 56 178 057 063 - ph: 04 1219 8888 - <a href="mailto:onno@itmaze.com.au" rel="noreferrer noreferrer" target="_blank">onno@itmaze.com.au</a></div></div></div></div></div>
_______________________________________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au" rel="noreferrer noreferrer" target="_blank">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.org.au" rel="noreferrer noreferrer" target="_blank">committee@plug.org.au</a><br>
PLUG Membership: <a href="http://www.plug.org.au/membership" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.plug.org.au/membership</a></blockquote></div>
_______________________________________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au" target="_blank" rel="noreferrer">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" rel="noreferrer noreferrer" target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.org.au" target="_blank" rel="noreferrer">committee@plug.org.au</a><br>
PLUG Membership: <a href="http://www.plug.org.au/membership" rel="noreferrer noreferrer" target="_blank">http://www.plug.org.au/membership</a></blockquote></div></div></div>