Manage access requests
Review incoming access requests, see what each shopper asked for, and send them a passcode or secret link.
Every time a shopper submits the request form on a Passcode- or Secret-link-protected lock (see Request access overview), it shows up in the Request access list, ready for you to review and act on.
The Request Access list
Open Request access from the app's main navigation. The list shows every submission with:
Name and Email — who asked.
Status — Pending (not yet actioned) or Access sent (you've already granted access).
Type — which access rule the request applies to (Passcode or Secret link).
Created at — when the request came in.
Use the tabs above the list to filter to All, Pending, or Access sent, and the search field to find a request by name or email. Select one or more rows to reveal a Delete request bulk action — deleting is permanent, so confirm you no longer need that request before removing it.

Opening a request
Click any row to open its detail page. At the top you'll see the locked resource the shopper was trying to reach — the product, collection, or page card (with its image, title, and other details), or a direct link to the locked URL if the lock doesn't target a single product, collection, or page. Below that, a card shows the lock's name, status, rule type, scope, and when it was created and last saved.
Granting access
On the request's detail page, the List access card shows the passcode or secret link you can send:
If the lock only has one active passcode or secret link, it's selected for you automatically, with a note confirming that.
If the lock has more than one, pick which one to send from the dropdown.
The information card next to it repeats the request's status, the shopper's email, name, the date they submitted it, and any message they included. When you're ready, click Send access. This emails the shopper the Customer access email with the passcode or secret link you selected, and flips the request's status to Access sent. If sending fails for any reason, an error banner explains what went wrong so you can try again.

Related docs
Last updated
Was this helpful?