1

After closing user membership, their data often needs to be anonymized (GDPR requirements). Of course, I understand their history with signatures and envelopes will still be present, but that's acceptable and reasonable for legal purposes. However, we would like to remove the user's full name, phone, company & job info from the closed profiles. Ideally, replacing their (now inactive) company email address with some dummy value also would be great.

Here's what I found and had some problems (and surprises) with:

  • I have to use CreateBulkImportSingleAccountUpdateUsersRequest method for updating even single users because eSignUserManagement:updateUser surprisingly does not include phone number field! No phone here https://developers.docusign.com/docs/admin-api/reference/usermanagement/esignusermanagement/updateuser/ nor do I see it in .net SDK data structures.

  • updating first name, last name, jobtitle, phone, company works fine through CreateBulkImportSingleAccountUpdateUsersRequest as long as the user is not closed (using CloseMemberships API method for closing). If the user is closed, then, surprisingly, their full name does not react to first name, last name changes. However, jobtitle, phone and company gets updated just fine.

Here's the example CSV I'm sending for update (all the data is faked for testing, so it's safe to share):

APIUserName,FirstName,LastName,UserEmail,eSignPermissionProfile,UserTitle,CompanyName,Phone
52f147f2-b7c6-480f-8e61-369fb7777777,Testersa,Docuapisa,ignore@nosuchmail.com,DocuSign Sender,Docusign APPA,Test ABBAR,+1234567555

It works fully and correctly when user is not closed.

Am I doing something wrong or it's "by design" that Full Name stops reflecting FirstName,LastName changes if the user is closed?

  • if I try to also change an email address in the CSV, then the batch request fails for closed users with "membership_not_in_account" error. I tried using UpdateEmailAddress API but that always returns Unauthorized error:
{"error":"unauthorized","error_description":"Not Authorized","reference_id":"..."}

Actually, I noticed that updating email does not work even when user is not closed. So I was wondering if it's caused by the fact that we have not yet configured Auto Activation properly? We are still in progress of setting up domains with SSO provider and require_identity_provider_auth. Will we be able to anonymize email addresses even for closed accounts when we get auto-activation feature working, or are closed accounts so special that they won't react to email updates?

I'm also highlighting some other Admin API inconsistencies below:

APIUserName,FirstName,LastName,UserEmail,eSignPermissionProfile,UserTitle,CompanyName,Phone
2ce69e93-983a-47f3-911a-995b29aeae2e,Tester,Docuapi,ignore2_dcs777@nosuchmail.com,DocuSign Sender,"Docusign ""Tester Ltd"" APP",Test AB,+1234567555

It fails because of "Docusign ""Tester Ltd"" APP" which has the outer double-quotes, according to RFC 4180 point 6, and also has inner quotes doubled as a means of escaping them, according to RFC 4180 point 7. Currently, I had to apply a workaround to our values to replace " with ' - then it works fine.

  • CreateBulkImportSingleAccountAddUsersRequest method lies about the update results (at least when using .net SDK). For example, after calling CreateBulkImportSingleAccountAddUsersRequest and then waiting for GetBulkUserImportRequest to return the final result, it returns UpdatedUserCount = 3 for the users that already existed on DocuSign, although no user data was actually updated. Of course, they should not be updated because it is AddUsers method and not UpdateUsers, but then the result should have UpdatedUserCount = 0 and not some other value. It makes sense also to check other Add/Update batch methods for their results being truthful to the actions performed, to avoid confusion of seeing updated / created counts for the methods with the opposite logic.
JustAMartin
  • 13,165
  • 18
  • 99
  • 183

0 Answers0