Playbook · Shopify collaborator request stuck pending

Shopify collaborator request / staff invite stuck pending or not accepted.

Written for a Shopify owner or ops lead whose collaborator request or staff invite stays Pending / Requested / not accepted so an agency cannot open the store Admin. DIY-first: prove the Users and permissions row vs Partner dashboard; fix wrong .myshopify.com URL, expired invite, owner never accepted, and Collaborators vs Staff Accounts mix-up. Distinct from POS Pro staff permissions wrong, custom app scopes missing, and admin app blank after install. No earnings claims, no invented case studies.

Nico at Latch AI Ops · Sep 10, 2026 · ~11 minute read

Buy the 72-hour install — $997Collaborator email not sendingStaff vs collaboratorMerchant FAQ

01

Collaborator / staff invite stuck Pending — not POS permissions, custom app scopes, or blank admin apps.

Several “agency cannot get in” bugs look alike. They do not share one fix. This page is only when Settings → Users and permissions shows a Collaborator request or Staff invite stuck Pending / Requested / not accepted — so the Partner or staff user still cannot open Admin for that store. When a POS Pro cashier is Active but cannot refund, discount, or open the cash drawer, open POS Pro staff permissions wrong. When a custom / private app is installed but Admin API scopes are missing after an update, open custom app scopes missing. When an embedded admin app paints a blank / white screen after install, open admin app blank after install. When the collaborator invite email never arrives, open collaborator request email not sending. Staff vs Collaborator role confusion without a stuck Pending state is staff account vs collaborator. This page is only: Shopify collaborator request / staff invite stuck pending or not accepted.

Six ordinary reasons the invite stays stuck: the request targeted the wrong .myshopify.com (dev store, typo, old transfer); the store owner never opened Settings → Users and permissions → Accept; the invite expired and was never resent; the agency mixed up a Staff account invite for an employee email with a Collaborator (Partner) request; the owner Declined and nobody re-requested; or you are debugging POS permissions / app scopes / blank App Bridge screens instead of the Pending row. Walk them in that order. You already pay for Shopify. You do not need another access SaaS to prove Pending becomes Active.

02

Prove Pending invite state and that agency Admin access is still blocked.

Owner: open Settings → Users and permissions. Note Collaborators and Staff separately. Screenshot any Pending / Requested row with the email or Partner account name and the timestamp. Agency: open the Partner dashboard for that exact store and confirm status is still Requested / Awaiting approval — not Active, not Declined.

If Admin already opens for the agency and the problem is cashier POS permissions, leave for POS Pro staff permissions wrong. If the invite email never landed in the owner inbox, open collaborator request email not sending. If access is Active but an embedded app is white, open admin app blank after install. Stay here only while the Collaborator / Staff row is still Pending and Admin is still blocked.

03

Fix wrong store URL, expired invite, owner never accepted, Collaborators vs Staff mix-up.

Confirm the collaborator request used the live .myshopify.com for the production store — not a development store, not a typo, not an old domain after a store transfer. Have the store owner click Accept on the Collaborators row (or the invite email) and grant the permission set the agency actually needs. If the invite shows Expired, revoke and send a fresh Collaborator request from the Partner account.

Do not confuse Collaborator (Partner) with a Staff account invite for an employee email — they are different rows and different acceptance paths. If the owner Declined, re-request after they confirm they want the agency in. Retest: the agency Partner account must open Admin for that store without a Pending badge. Soft note: Latch’s 72-hour install also starts when collaborator access is in — same Access path, not a second product.

04

Checklist and how to prove the agency can open Admin.

Checklist: (1) screenshot Users and permissions Collaborators / Staff Pending rows, (2) confirm Partner dashboard still shows Requested for the exact .myshopify.com, (3) verify store URL is production not a dev clone, (4) owner Accepts with needed permissions, (5) resend if Expired, (6) stop mixing Staff employee invites with Collaborator Partner requests, (7) retest agency Admin login, (8) if Active but POS / scopes / blank app remain wrong, switch playbooks.

Prove it: after Accept, Settings → Users and permissions must show the Collaborator / Staff user as Active, and the agency must open Admin without a Pending / Requested state. If Active access exists but POS Pro cashiers still cannot refund, open POS Pro staff permissions wrong. If a custom app is Active but scopes are missing, open custom app scopes missing.

05

You tested POS Pro permissions, custom app scopes, or blank admin apps instead.

POS Pro staff roles that cannot refund / discount / open the drawer are POS Pro staff permissions wrong. Custom / private app missing API scopes after update is custom app scopes missing. Embedded admin app blank / white screen after install is admin app blank after install. Collaborator invite email never arriving is collaborator request email not sending. None of those fix a Collaborator / Staff invite that is still Pending so the agency cannot open Admin at all.

Finish prove Pending row + blocked Admin → correct store URL / Accept / resend → Active access proof first. Only then open the related playbook that matches the remaining symptom.

06

When to stay DIY vs pay $997.

Stay DIY if you can spend one afternoon on the list above: prove Pending Collaborator / Staff vs Partner Requested, fix the store URL, have the owner Accept, resend expired invites, stop mixing Staff with Collaborator, and stop treating POS permissions / custom app scopes / blank admin apps as the same bug. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: POS Pro permissions, Custom app scopes, Admin app blank, Collaborator email.

Pay $997 when the gap is wiring the stack you already pay for once collaborator access is in — lead capture, ops alerts, checkout-ready workflow on the live store. Latch install uses collaborator access; the 72-hour clock starts when that access is in. One live store. No earnings claims, no ticket-cut promises, no recovered-revenue math. Checkout: https://whop.com/checkout/plan_jHoFkwA8EXHTD.

Buy the 72-hour install — $997HomeFAQ

Nico at Latch AI Ops · Updated 2026-09-10 · DIY-first · No earnings claims