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

​
Quick reference: Bitbucket

​
Status Notifications

Configure how StagingPro pushes events to your team. See notifications, email, Slack, Teams for per-channel setup mechanics. Tip: set up at least two channels for redundancy on Production-related events.

​
Configuration Settings (config.json)

The Configuration Settings tab displays the theme config values pulled from your BigCommerce store’s active theme config.json. StagingPro syncs this file automatically into the connected GitHub repository so it stays in step with what BigCommerce has. Click Update config.json from this tab to:
  • Add or update configuration values.
  • Specify custom CRM or ERP URLs and API keys.
  • Extend theme configuration as needed.
Changes pushed via this tab flow back through the same Git deploy pipeline so they appear in history and rollback for auditability.

​
B2B Edition

The B2B Edition tab lists every environment with columns for store ID, store URL, the B2B email, the B2B password, and Connect / Disconnect actions. See B2B, coupons, and data dependencies for the full B2B setup including the manual user creation flow that B2B Edition requires. After connect, the action button changes to Connected in green. B2B entities only appear on Bulk Content Migration when the relevant environment shows Connected.

​
Connect Agency

This tab lets you grant external agency partners access to your StagingPro tenant. Useful when you have hired an agency to manage your BigCommerce theme work.

​
Adding an agency

  1. Enter the Agency Name.
  2. Enter the Agency Email.
  3. Click Add.
The agency receives an invitation. They appear in the Agency Access list once they complete onboarding.

​
Agency Access list columns

​
Approving inbound agency requests

If an agency requests access to your store, the request appears at the top of the Connect Agency tab. Review the agency details and click Approve to grant access or Reject to deny.

​
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.

​
VIQ Agency

The VIQ Agency tab manages integrations with Vortex IQ agency-tier services. The grid columns mirror the Connect Agency tab. Pending requests show approval / reject options at the top. 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 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.
  • Scheduling, use it for any Bulk migration that exceeds 30 minutes of expected runtime.