This should be possible with Search Page asset and a Standard Page (optional).
1/ HTML Search Form
First create optional Standard Page with simple input for email search with POST to the Search Page.
<form enctype="multipart/form-data" action="/dev/users/search-user" method="post">
<p><input type="text" name="user" placeholder="input your email address" /></p>
<p><button name="submit" type="submit">GET DOCS</button></p>
2.1 / Search Page: Search Fields
- Name: anything e.g staff
- Type: asset attribute
- Details: asset type: user and attribute: email
2.2 / Search Page: Details Screen
- Root Nodes: To all or specific user group
- Asset per page: 1
- Stored Query Location: Select the name of Search Field with Post Variable Name, in this example user (same as the standard page input field name)
- Stored Search Options: Results page
2.3 / Search Page: Default Type Format
This is optional if the user(s) is found by the search so you can display the links or docs. But it can be used as secondary way of validating the search email matches the result and then display the items.
<p>Access to wonderful things.</p>
<p>Oops, we don't recognise you.</p>
The reason why I prefer to use Standard Page to perform the search as opposed to just doing it with the Search Page itself is because if you have Analytics or any tracking tools the results of the page in the URL parameter gets indexed so by using POST the email is kept hidden.