Best practice - de-provision users
We are trying to automate the de-provisioning process for terminated employees. What we currently do is delete the user and move their data to a de-provisioning account to hold for 30 days. That part is working fine...
The part I am trying to work out now would be to use the API to get a list of all files/folders that have collaborators or are shared, and save that information in an XML file. Then remove all the collaborators/sharing. Is that possible through the API?
The idea is that if someone in the company still needs that data, we can share it back out from the de-provisioning account once we verify that it has been shared out.
-
You can get a list of collaborations for individual files and folders using these two endpoints:
Get File Collaborations and Get Folder Collaborations. In terms of workflow, you would first have to get a list of all the files and folders in a user's account by recursively calling the Get Folder Items endpoint. Then, you would check to see if those items have collaborations with the Get File Collaborations and Get Folder Collaborations endpoints.
サインインしてコメントを残してください。
コメント
1件のコメント