{subsection: What if someone leaves the UW?}
 
-The big problem is maintaining access to files (and maybe even the shared folder) if the owner leaves the UW.  It's not clear what will happen to such files or folders.  They might stay available.  They might disappear.
-
-Testing with just deleting a shared folder, it looks like documents owned by other people are put in the top level of the owner's documents.  They're not lost.  _Presumably_ having an account closed will do no worse than this.
-
-Alan has a query in to DoIT to find out the exact behavior.
-
-We can download final versions and attach them to tickets, but it would be a shame to get so far and miss the final step.
+DoIT Help Desk said, in a June 19th, 2013 message to Alan ("Subject: Re: UW Madison Google Apps: ensuring documents survive a team member leaving(Case 618712)"):
+{blockquote}
+If a file owned by the user who leaves (we'll continue with your "bucky"
+example), is saved in the google group, the file will remain, even after
+bucky has left the University. The other team members won't be able to
+edit this document, unless they were given editing privileges before
+bucky left. Alternatively, if you need to give people editing
+privileges, you can copy the document and another member of the team can
+just recreate it with themselves as the owner, adding in editors as
+needed. Folders shared by bucky will also remain even after he leaves.
+{endblockquote}
 
 {subsection: What if someone closes their non-UW account?}
 
-The problem is similar to "What if someone leaves the UW?", but we may have even less control.  (Being a UW account may come with additional control over files.)  Shouldn't be a problem for the folder; we'll just ensure it's a UW account.  But it seems likely that non-UW staff will occasionally create design documents.
+Probably unlikely; how often does someone close their Google account?  But there is a risk we'd lose the documents.  Proposed: documents must be owned by someone using a UW account.  Likely flow: non-UW member creates the file and works on it.  Eventually someone from the UW copies the file and that becomes the official copy.
 
 {subsection: Offline support}