Collaborator access
A Collaborator is someone from another org who's been granted operational access to your org, typically an agency working on your store. They can do the work; they can't change billing or remove your team.
How it gets created
Two paths:
- Agency handoff. An agency builds a store inside their own org, then hands it off to you via a handoff invite. If they chose the partner mode at invite time, a Collaboration row is created automatically, and they keep operational access on your new org.
- Direct invite. You (the merchant) invite a partner from the Collaborations page. Click Invite a collaborator, paste their referral code, and send. They get a pending invite on their side; when their owner accepts, the Collaboration goes live.
What a Collaborator can do
Every operational surface: items, search settings, merchandising rules, intelligence, reports, Shopify configuration. Anything that affects what your shoppers see and how your catalog behaves.
What a Collaborator can't do
- Change your billing plan or payment method.
- Invite or remove members of your org.
- Disconnect your Shopify or Stripe integrations.
- Rename or delete the org.
These are reserved for your org's owners. The split exists so an agency can do their job without becoming a billing or governance party to your org.
API keys created by Collaborators
If a Collaborator creates an API key on your property (say, for an integration they're wiring up), it's tagged with their agency's org id. If you later revoke their Collaboration, every key they created auto-revokes too. Keys your own team created aren't affected.
You can see which org created each key on the property's Settings page.
Revoking a Collaboration
From the Collaborations page, find the Collaborators on your properties panel and click Revoke on the row. The agency loses access immediately. Their API keys (the ones they created on your property) get revoked in the same action.
If the agency had Attribution on your org (earning rev share), revoking the Collaboration doesn't touch the rev share. Attribution and Collaboration are independent. They keep earning unless the Attribution is also terminated, which is a separate VeryQuery-internal action.
Scoping to specific team members
By default, every member of the partner agency's org gets Collaborator access on your org. The data model also supports restricting to specific team members from the agency, but we haven't shipped the UI for it yet. Ask if you need it.
Multiple agencies
You can have any number of active Collaborations at the same time. Each is independently revocable. If you fire Agency A and hire Agency B, you revoke A's Collaboration and accept B's invite. The rev-share attribution stays with whoever brought you in originally.