Verify your contact's identity

[earakel]

No description provided.

[jorge-campo]

Thanks for this content, Emma – The content is great, but I have several additions to the article.

Let's start with content organization

By reading this article, I realized we need another one to inform users how to respond to a contact verification request.

This new and additional article will be much simple: an intro explaining what's a "verification request" and two short procedures:

1. Explain to the user how to accept or reject the request.
2. Explain where I can see the list of requests I've declined (this is one of the screens in the notifications settings; ask Fabio if you can't find the Figme. He's working with these screens.)

Please, add this to the mind map. If I were you, I'd start with this article right away now that you have this content fresh in your mind.

About the workflow

• I still think this article will improve by using an illustration depicting the workflow steps. Please, create an update issue in our GitHub project board so we can update the article after the MVP with this workflow.

• Step 1 – In the last step or right after the procedure but before the tip admonition, indicate that the other person receives an identity verification notification. This is obvious, but nevertheless helpful to remind.

• Step 2 – You say, "Wait until your contact responds to your question." We need to explain and add here answers to these questions:

  • What happens if they don't respond to my request?
  • Can I check the status of this verification request? (Yes, I can) How?
  • Can I send another verification request if I don't receive an answer?
  • If the other person rejects my request, do I get any notification? (according to the Figma workflow here, I don't. But some of these workflows are out of date.)

-> Alisher can help you to answer all these questions.

About the content.

I have only some minor changes to the content. I believe your content can improve in terms of predictability, so a user sending a verification request can know what's going on at each stage (to the extent they can/should know.)

Intro

This is something you mention in the intro, but it's a very important piece of information, and we should mention this again in a note-style admonition right before "What to expect": Marking someone as Untrusted is not the same as blocking someone, and doesn't change in any way my connection to this contact.

What to expect

• "What to expect" title is an H2, not H3 (I believe this is a mistake on the style guide that I need to update.)
• "You can mark someone aw untrusted..." -> "You can mark someone as untrusted..."

Step 3

• you mark them with the Trusted label. -> ... you mark the contact with the Trusted label. And you can include a link to the article explaining how to use labels.

• "If not, you mark them as untrusted and can either keep them as a contact, remove them from your contacts or block them." This sentence is the perfect place to link to other content; "remove them from your contacts" and "block them" should link to Remove a contact from Status and Block or unblock someone in Status, respectively.

• The :desktop-verify-identity: icon in the desktop procedure is missing. As far as I can see, it's not on the repo or your PR.

• "Click their name at the top." -> "Click their name at the top of the content area."

• "Click more options." -> "On the contact's card, click more options". There are two more options on the same screen; clarifying which one we're talking about is always good.

• (Mobile) "Review their response and tap either Decline or Mark as trusted." Please, double-check with Alisher what are the final labels for these two actions. (The ones that you include aren't the ones in Figma.

[jorge-campo]

Hi @earakel – Could you please update and close this PR with the latest changes? Thanks.

[earakel]

I closed this PR earlier and will be sending a new one that includes recent changes shortly!