> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# StagingPro Settings and Scheduling, BigCommerce Configuration Reference

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:

| Tab                        | Purpose                                              |
| -------------------------- | ---------------------------------------------------- |
| **Connect Repository**     | Link GitHub or Bitbucket; manage team members        |
| **Status Notifications**   | Configure email, Slack, Teams alerts                 |
| **Configuration Settings** | View and update theme `config.json` from BigCommerce |
| **B2B Edition**            | Per-environment B2B credentials                      |
| **Connect Agency**         | Grant external agency partner access                 |
| **VIQ Agency**             | Manage Vortex IQ agency integrations                 |

## 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](/vortex-apps/staging-pro/github-and-bitbucket) for the full setup walkthrough.

### Quick reference: GitHub Apps

| Action             | Where                                                     |
| ------------------ | --------------------------------------------------------- |
| Connect GitHub App | Settings, Connect Repository, Connect to GitHub App       |
| Add Team Member    | Connected repo view, Add Team Member button               |
| Change Permission  | Per team member row, Change Permission                    |
| Remove Member      | Per team member row, Remove (does not remove from GitHub) |

### Quick reference: Bitbucket

| Action                           | Detail                                                                         |
| -------------------------------- | ------------------------------------------------------------------------------ |
| Invite StagingPro Bitbucket user | Invite `bitbucket@stagingpro.com` to your Bitbucket workspace as admin         |
| Repository URL format            | workspace/repository, e.g. `themedeploy-stagingpro/stagingpro-repo`            |
| Verify                           | Click **Verify Bitbucket Account** after entering the URL                      |
| Add Team Member                  | Enter Bitbucket username and Bitbucket name (from personal Bitbucket settings) |

## Status Notifications

Configure how StagingPro pushes events to your team. See [notifications, email, Slack, Teams](/vortex-apps/staging-pro/notifications-email-slack-teams) for per-channel setup mechanics.

| Notification type            | Triggered by                                              |
| ---------------------------- | --------------------------------------------------------- |
| Deployment Notifications     | Theme deployment events (start, complete, fail, rollback) |
| Data Migration Notifications | Bulk and selective content migration events               |

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](/vortex-apps/staging-pro/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](/vortex-apps/staging-pro/b2b-coupons-and-data) for the full B2B setup including the manual user creation flow that B2B Edition requires.

| Column    | Meaning                                           |
| --------- | ------------------------------------------------- |
| Type      | Environment type (Production, Staging, UAT, etc.) |
| Store ID  | BigCommerce store hash                            |
| Store URL | Link to the store                                 |
| Email ID  | B2B Edition login email                           |
| Password  | B2B Edition password                              |
| Actions   | Connect / Disconnect                              |

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

| Column        | Meaning                                                                      |
| ------------- | ---------------------------------------------------------------------------- |
| Agency Name   | Name of the agency partner                                                   |
| Email         | Agency contact email                                                         |
| Status        | Toggle (Active / Disabled), or Pending Approval / Rejected during invitation |
| Date Created  | When access was granted                                                      |
| Date Modified | Last update timestamp                                                        |

### 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](https://www.vortexiq.ai/) 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.