Sharetribe: grant access after verification

This page is the second of two steps. The Zap from Send the verification link sends each new user a verification link. Here you build two Zaps that act on the result:

• ProofAge 2 – Approve verified user: when a verification is approved, approve the user and/or grant permissions, and tell them by email.
• ProofAge 3 – Email declined user: when a verification is declined, tell the user and link your “verification failed” page.

​

What you need

• Everything from Send the verification link, with the first Zap turned on.
• A finished test verification. Use the test user from the first page: open the link in their verification email and go through the screens. In a test workspace nothing is analysed, so any ID document works. If you already used that link, sign up a new test user and wait for their email.
• Your Sharetribe and ProofAge connections in Zapier from the first page.

​

Choose the result of a test verification

In a test workspace ProofAge never decides on its own. Every finished verification waits with the status Review until you choose its result. Do this once now, so the trigger in the next section has a result to find:

1. In Sharetribe Console, copy your test user’s ID: go to Users, click the user and copy the User ID.
2. In the ProofAge console, open Verifications and paste the ID into the search box. The verification shows up with the result In review. The External ID column holds the Sharetribe user ID.
3. Click the verification to open it.
4. Click Approve at the top right. It takes effect right away, without a confirmation.

ProofAge sends the result to Zapier right away. Two more buttons sit next to Approve. You’ll use Decline for Zap 3. Failed marks the verification as failed. None of the Zaps in this guide reacts to it, so you don’t need it here.

​

Creating Zap 2, step by step

In Zapier, click + Create, choose Zaps and name the new Zap ProofAge 2 – Approve verified user.

​

Step 1: Verification approved trigger

1. As the trigger app, choose ProofAge. As the trigger event, choose Verification Completed.
2. Choose your ProofAge connection, “Your workspace name (Test)”.
3. In Configure:
   • Status: Approved. The Zap then runs only for approved verifications, so you don’t need a separate Filter step for this.
   • Include Extracted Document Data: leave it False. Zapier then receives only the result and your user’s ID, never their name, birth date or document number.
4. Click Test trigger and pick the verification you approved. Check that External Reference contains a Sharetribe user ID.

This trigger is instant: ProofAge notifies Zapier the moment a verification is decided, so there’s no polling delay.

​

Step 2: Look up the user in Sharetribe

1. Add an action step with Sharetribe and choose Show User.
2. Choose your Sharetribe connection. Check that it’s the Test environment.
3. User ID: choose External Reference from step 1.
4. Leave the other fields as they are and click Test step. You should see your test user, including their email address and name.

​

Step 3: Approve the user

Use this step only if new users need approval to join your marketplace (Approve users who want to join in Access control). Approve User only works on users who are pending approval. If your marketplace doesn’t require approval to join, skip this step and use step 4 only. Before the step runs, the user looks like this in Sharetribe Console, under Users:

1. Add an action step with Sharetribe and choose Approve User.
2. User ID: choose External Reference from step 1.
3. Click Test step. The Test tab gets a tick, and Data out shows the user’s ID. The test user is now approved: in Sharetribe Console, under Users, the Pending approval label next to them is gone (their User State changes from pendingApproval to active).
   Testing this step really approves your test user. To test the Zap again later, sign up a new test user.

​

Step 4: Grant permissions

Use this step if you restricted posting listings or starting transactions in Access control.

1. Add an action step with Sharetribe and choose Update Permissions.
2. User ID: choose External Reference from step 1.
3. Set Permission to post listings and Permission to initiate transactions to True. Leave Permission to view listings empty unless you restricted viewing.
4. Click Test step. In Sharetribe Console, under Users, the Post listings and Initiate transactions columns now show a tick for the test user.

​

Step 5: Tell the user they’re verified

1. Add an action step with Gmail and choose Send Email.
2. To: click + and choose User Email from step 2 (Show User).
3. Subject: for example Your Marketplace: you're verified!
4. Body: for example:

   Hi [2. User Profile First Name], your identity has been verified and your account is ready. You can now post listings and make bookings: https://your-marketplace.com – The Your Marketplace team

   
5. Click Test step and check that the email arrives in the test user’s inbox.
6. Click Publish to turn the Zap on.

The finished Zap has five steps:

​

Creating Zap 3: email users whose verification was declined

Zap 3 is a shorter copy of Zap 2, so you don’t build it from scratch.

1. On your Zaps page, open the ⋮ menu of ProofAge 2 – Approve verified user, choose Duplicate, then Duplicate and edit. The copy opens as “(Copy) ProofAge 2 – Approve verified user”.
2. Click the copy’s name, choose Rename and name it ProofAge 3 – Email declined user.
3. Delete Update Permissions and Approve User: open each step’s ⋮ menu, choose Delete and click again on Really delete?. Keep Show User and the email step.
4. Open the trigger and change Status to Declined.
5. Open the email step. Change the Subject, for example Your Marketplace: we couldn't verify your identity, and the Body, for example:

   Hi [2. User Profile First Name], unfortunately we couldn’t verify your identity. You can read what to do next here: https://your-marketplace.com/p/verification-failed If you think this is a mistake, reply to this email and we’ll send you a new link.

6. Give the trigger a declined verification to test with. Zapier won’t publish the copy without one.
   1. Sign up another test user and finish their verification.
   2. In the ProofAge console, open that verification and click Decline.
   3. In Zapier, open the trigger’s Test tab, click Find new records and pick the new record. Its Status is declined.
7. Test the email step and check that the email arrives.
8. Click Publish.

ProofAge doesn’t tell the user why they were declined. When ProofAge makes the decision, the Reason Code field of the trigger gives the decision reason, for example an expired document or a face that doesn’t match the ID. Keep it for your own team, for example in an internal notification. A verification you decline by hand in the console has no reason code.

​

Test the whole flow

With all three Zaps on, test each case in your Test environment: Zapier’s Zap history shows every run; the ProofAge console shows each verification and whether its result reached Zapier. How long it takes: the verification email arrives within one Sharetribe polling interval after sign-up. Zapier shows the interval on the trigger (2 minutes on the Professional plan). In our test it took between 10 seconds and a minute and a half. After the decision, Zap 2 or Zap 3 runs within seconds. In our test the user’s access changed and the email went out 6 to 22 seconds after we clicked Approve or Decline. Each user who gets verified uses 6 Zapier tasks (2 in Zap 1 and 4 in Zap 2); a declined user uses 4.

​

Let a user try again

A declined verification can’t be reused. To give a user another chance:

1. In the ProofAge console, open Verifications and click New link.
2. Under Workspace, choose the workspace your Zaps are connected to.
3. In Your reference, enter the user’s Sharetribe user ID (copy it from Sharetribe Console: Users, click the user, User ID). This is what links the new result to the user, so it must be exactly the user ID.
4. Click Create link. ProofAge shows the link, a QR code and how long the link is valid. Click the copy button next to the link and send it to the user, for example in a reply to their email.

When the user finishes, they land on the Redirect URL you set on the workspace on the first page, and Zap 2 or Zap 3 handles the result as before. We don’t recommend sending a new link automatically with every decline: each attempt counts as a verification (billed once your free ones are used), and people declined for fraud would get unlimited tries. If ProofAge asks the user to retake a photo (for example because it was blurry), they can do it right away on the same link. There’s nothing to set up for that.

​

Next

Your marketplace now verifies new users and grants access automatically. When everything works in Test, follow Go live in the overview. If something doesn’t work, see Troubleshooting there. Questions about ProofAge: [email protected]. Questions about your marketplace or Zapier: contact Sharetribe from your Console.