Handle users with multiple accounts

[virgile-dev]

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe.
On our instance docs.numerique.gouv.fr people with multiple email adresses have created multiple accounts on Docs.
This leads to not knowing which user to invite on the docs has we have multiple results for one individual and also we for the user not knowing on which account a document has been shared and having to ask "can you invite me on this address instead?

Describe the solution you'd like
While this is an issue created by the user and the identity provider it would be nice to have an internal tool that help handles this situation in the short term.

When a user contacts the admin telling him he'd like to have his account(s) deleted / disabled in favor of another account he's actually actively using we should be able to run a task in the db where :

• owner the document he created change ownership to the account he's using
• member his memberships and associated roles to documents he hasn't created get attributed to the account he's actively using -
• access request : a user can request access to a doc, we should update this access request with the account the user is actively using

When need to think about the emails the application sends, we don't want to flood the user with invitation emails.
So I'd be in favour of sending a digest instead. Recaping all the documents the user access after running the procedure.

We also need to think of who can run this task, only a sysadmin or someone with a django admin access which would mean we need to do UI for this. I'm in favour of doing the first option at first.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Discovery, Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and possibly write out some documentation (if applicable).
Maybe add a screenshot or design?

Do you want to work on it through a Pull Request?

[Ash-Crow]

Tickets regarding the GDPR side of things:

• Delete my account #1110 for the deletion of a user account
• GDPR compliance: Allow the export of user data #1647 for the request of user data

(ping @virgile-dev)

[Ash-Crow]

Doc listing the detailed proposal

It suggests to use Démarches simplifiées for the form asking the email but:

• creating a form on Démarches simplifiées requires a lot info, including a link to the "cadre légal". That's quite an overhead for a form with a single field (the email address that will be "reconciliated" and deactivated)
• we would still need to match the email address used to make the démarche with an account and check that it's an active one.
• we would need to integrate calls to the Démarches simplifiées API, which I can't find being used for now.
• it would also impair third party users of Docs, as they can't rely on Démarches simplifiées.
• even in the official instance of Docs it would impair non-French speakers as it doesn't seem that Démarche simplifiées support multilingual forms.

for these reasons, I believe the whole process should happen inside Docs.

What do you think @virgile-dev @lunika ?

[virgile-dev]

Hey @Ash-Crow
Let's focus here on how form a table taking this format

emails_used	emails_not_used	link_clicked

You can run a reconcialiation task. How emails get into that table is left to the Docs admin to decide. We'll use Démarches Simplifiées cause we run the DINUM instance. If API Aren't available maybe let's just start by working with csv import that should work for everyone.

[Ash-Crow]

When updating the document access, I run into the case where the user has access to a document with both the active_address (the one we'll keep) and the inactive address (the one we'll not keep), with potentially different roles (eg, "editor" vs "owner")

I suggest we put the active_address with the higher role and remove the other one. What do you think @virgile-dev?

[virgile-dev]

@Ash-Crow uh nice catch. yep agreed !

[Ash-Crow]

Another edge-case related question:

• What do we do if we have conflicting requests (eg. user wants Email address 1 to be merged into Email address 2 and then requests the reverse (Email address 1 to Email address 2) or even request either both to Email address 3)