Skip to main content
Settings is where you configure StagingPro to match your team’s workflow: where the code lives, where notifications go, B2B Edition credentials, agency partner access, and the Vortex IQ agency integration. Scheduling is a Premium feature that lets you queue bulk and selective migrations for off-peak windows. This page is the combined reference.

​
Settings tabs at a glance

The Settings page is organised into six tabs:

​
Connect Repository

The repository tab lets you link the Git provider for theme deployments. StagingPro supports GitHub Apps (recommended) and Bitbucket. See GitHub and Bitbucket for the full setup walkthrough.

​
Quick reference: GitHub Apps

​
Status Notifications

Configure how StagingPro pushes events to your team. See notifications, email, Slack, Teams for per-channel setup mechanics.

​
B2B Edition

This tab is obsolete in StagingPro V2 and slated for removal. V2 migrates B2B Edition data through the store’s main API token (created with the B2B Edition scope) — no per-environment B2B email/password connection is needed, and any values entered on this tab are ignored. See B2B, coupons, and data dependencies for the current prerequisites.
The B2B entities appear on Bulk Content Migration automatically when both the source and destination stores are on B2B Edition and their API tokens carry the B2B scope.

​
VIQ Agency

The VIQ Agency tab manages integrations with Vortex IQ agency-tier services. If an agency requests access to your store, the request appears at the top of the VIQ Agency tab. Review the agency details and click Approve to grant access or Reject to deny. This tab is relevant if you have engaged Vortex IQ for managed services or if a VIQ-tier agency is operating your store on your behalf.

​
Best practices for agency access

  • Grant access only to agency partners you have a contractual relationship with.
  • Review the agency access list periodically and remove access when partnerships end.
  • Restrict Production-environment access to only the agency members who genuinely need it; use the GitHub Change Permission flow to scope developers to Staging and UAT.

​
Best practices summary

  • Notifications, set up at least one channel before running migrations. Set up Slack or Teams for shared visibility.
  • Repository, use GitHub Apps over manual PAT setup. Add team members for everyone who will commit.
  • B2B, ensure credentials are current per environment. Re-test connections after any password change in BigCommerce B2B Edition.
  • Agency access, audit periodically; remove access when partnerships end.