Collaborations

Collaborations are access relationships with merchant-owned stores. When you have collaborator access to a store, it appears in the Dev Dashboard's Stores list as a Collaboration. Unlike dev stores and client transfer stores, you don't own a collaboration store; the merchant does. You're working inside their live store.

Collaborator access reaches only the parts of a store the merchant grants, and it doesn't count toward the store's staff limit. To explain that to a merchant, send them the Help Center page on collaborator accounts.

Use collaborations when an existing merchant needs support, customization, or app development on their store.

Anchor to RequirementsRequirements

Before you begin, make sure you have:

• A Shopify Partner account.
• The required permissions to manage collaborations in your organization.
• A verified identity, if Shopify requires one of your organization. When it's required, the request page says so, and you can't send the request until you verify. Refer to Verifying your identity.

Anchor to Request collaborator accessRequest collaborator access

To request access to a merchant's store:

1. Log in to the Dev Dashboard.
2. Select Stores from the left sidebar.
3. Select Request store access.
4. Enter the store's permanent myshopify.com URL. Custom or secondary domains aren't supported.
5. Enter the merchant's 4-digit collaborator request code. The merchant can find this in their Shopify admin under Settings > Users > Security. If they've never shared it before, they may need to locate and share it with you first.
6. Select the permissions you need.
7. Select Send request.

The merchant receives a request to grant your organization collaborator access. Once they approve it, the store appears in your Stores list with the status Active.

Anchor to Request access from an app's Installs pageRequest access from an app's Installs page

When a merchant reports a problem with your app, you can request access to their store without leaving the app you're debugging.

1. Open the app in the Dev Dashboard and go to its Installs page.
2. Find the merchant's store and open its Store actions menu.
3. Select Request store access. The request form opens with the store's URL already filled in.
4. Select the permissions you need, and then select Send request.

The menu only offers Request store access for a store you can't already reach. For a store your organization already has access to, it offers Log in instead.

Anchor to Limits on requesting accessLimits on requesting access

The following limits apply when you send a request:

• A store can have a maximum of two pending collaborator requests at a time, counting requests from every organization. If a store is already at that limit, then your request fails until one of those requests is resolved.
• Your organization can have a maximum of 10 pending requests at a time, counting only requests that needed no collaborator request code. The limit doesn't apply when you enter a code, or when the store already has one of your organization's apps installed.
• Your organization must be at least 30 days old to send a request, unless the store requires a collaborator request code or already has one of your organization's apps installed.
• If a staff member on the store uses your organization's partner business email, then your request fails. Ask the store owner to remove that account.

Anchor to Collaboration statusesCollaboration statuses

You can track the status of your collaborations in the Status column of the Stores list, filtering by Type is Collaboration to see only these:

Collaborator access expires when nobody from your organization logs into the store for 90 days. Logging in at least once in that window keeps it active.

If the merchant declined your request by mistake, then you can't clear the request yourself. Refer to the Help Center's collaborator FAQs for how a merchant can recover a rejected request.

The Plan column is only populated for Active collaborations. A merchant's plan is hidden while a collaboration isn't active, so rows with any other status show a dash there as well.

Anchor to Cancel a pending requestCancel a pending request

While a request is waiting for the merchant to approve it, you can withdraw it.

1. In the Stores list, filter by Type is Collaboration and find the store with Request sent status.
2. Select the three-dot menu (⋯) on the store's row.
3. Select Cancel request, and then confirm in the Cancel collaboration request dialog.

If the menu offers Re-request access instead of Cancel request, that row is an expired collaboration that's already been re-requested, not a new request. Refer to Renew expired access.

Anchor to Renew expired accessRenew expired access

If your collaborator access has expired, you can send the merchant a new request directly from the Dev Dashboard.

1. In the Stores list, filter by Type is Collaboration and find the store with Access expired status.
2. Select the three-dot menu (⋯) on the store's row.
3. Select Re-request access.

The merchant receives a new request to approve. Once they approve it, your access is restored and the status updates accordingly.

Anchor to Remove collaborator accessRemove collaborator access

If you no longer need to work on a merchant's store, you can end the collaboration. This removes your whole organization's access to the store, not only your own, and it's available whether the collaboration is Active or Access expired.

1. In the Stores list, filter by Type is Collaboration and find the store.
2. Select the three-dot menu (⋯) on the store's row.
3. Select Remove access, and then confirm in the Remove collaborator access dialog.

To work on the store again afterward, request access the same way you would for a store you've never worked on.

Anchor to LimitationsLimitations

As a collaborator, your access is granted and controlled by the merchant:

• The merchant sets the scope of your permissions. You can only access the parts of the store they've granted you access to.
• You can't transfer a collaboration store. If the merchant wants to hand off store ownership, that's a separate process they initiate.

Anchor to Next stepsNext steps

• Create a client transfer store to build a store and hand it off to a client.
• Configure user permissions to manage who can request collaborator access in your organization.