Illustrative idea · ACCOUNT SECURITY
Review an account recovery request
Give an account owner a clear verification summary before recovery is approved.
Confirm identity through two channels—and keep access under human control.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Guide a person through separate phone and email checks using details they provide and verification codes delivered to them. Show whether each check was completed, but treat that result as one part of identity review: an authorized person must approve account access, recovery, or other security changes separately.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
Identity check requestA person’s submitted contact details and request to verify their identity
“Coordinate phone and email verification, make incomplete or mismatched checks visible, and hold account access or security changes for authorized human approval.”
Work through the request.
Clear tasks, with review where it matters.
- Receive an identity check request
- Verify access to the phone number
- Verify access to the email address
A clear status for each verification step, ready for an authorized reviewer; verification alone does not grant or change account access.
What this workflow could do
Helps a person complete a two-channel identity check and gives an account owner a reviewable result before security decisions are made.
Review points proposed in this idea
Verification codes and contact details are sensitive, and a completed check does not by itself establish that an account change is safe. Keep codes private, confirm that the requester is entitled to use the account, and require an authorized person to approve sign-in recovery, access changes, or other security actions.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Confirm which person and account the request concerns and collect only the contact details needed for the check.
-
Deliver a short-lived code to the submitted number and ask the person to enter the code they received.
-
Send a separate code to the submitted email address and check the person’s response without exposing the code to others.
-
Keep each result visible and route failed, repeated, or unexpected attempts to an authorized reviewer.
-
Require an authorized person to confirm the identity and approve any sign-in, recovery, or access change before it takes effect.
Step 1 of 5
Receive an identity check request
Confirm which person and account the request concerns and collect only the contact details needed for the check.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Define the identity review process
Choose which people and requests use the two-channel check and what additional evidence an account owner may need.
- 02
Set code and privacy practices
Use short-lived codes, limit who can view contact details, and make sure verification information is not included in general alerts.
- 03
Assign security approvers
Name the authorized people who can approve account access, recovery, and security changes after reviewing the verification result.
- 04
Test failed and unexpected attempts
Check mistyped details, expired codes, repeated attempts, and requests for another person; confirm the process stops for human review.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation