Title: Connector Controls
Author: Jacob
Published: November 10, 2026

---

 1. [Integrations](https://docs.wpvip.com/integrations/)
 2. [Integrations Center](https://docs.wpvip.com/integrations/center/)
 3. Connector Controls

#  Connector Controls

**Connector Controls** is an integration that centrally manages credentials for 
the 3 AI connectors WordPress Core ships: OpenAI, Anthropic, and Google.

Instead of pasting an API key into the WordPress Admin dashboard’s **Connectors**
screen on every site, credentials can be added once in the VIP Dashboard, then used
organization-wide or assigned to an environment or individual network site.

**Note**

Connector Controls manages only the 3 connectors WordPress Core ships. A custom 
connector that a plugin registers for itself remains configured on WP Admin’s **
Connectors** screen.

## Prerequisites

 * An environment must run WordPress 7.0 or later for its managed connectors to 
   operate. Credentials and assignments can be saved on an earlier version, but 
   nothing is delivered to WordPress until the environment is updated.
 * Connector Controls must be activated for the organization before an environment
   or network site can configure it. See [Add an integration to an organization](https://docs.wpvip.com/integrations/center/add-an-integration/).

## Limitations

 * Connector Controls manages credentials for `openai`, `anthropic`, and `google`
   connectors only. Other connectors registered by plugins are not affected.
 * Credentials can only be created at the organization or environment level.
 * An environment variable or PHP constant already set for a provider always takes
   precedence over anything assigned in Connector Controls. See [Credential inheritance](https://docs.wpvip.com/integrations/center/connector-controls?output_format=md#credential-inheritance)
   below.
 * Removing a credential does not automatically unassign it. An admin has to explicitly
   assign or unassign credentials.

## Roles and permissions

Activating Connector Controls for an organization requires the [Org admin role](https://docs.wpvip.com/manage-user-access/vip-dashboard/org-roles/).
Adding credentials and setting assignments at the environment or network-site level
requires [App admin access](https://docs.wpvip.com/manage-user-access/vip-dashboard/app-role/)
to that application.

## Credential inheritance

Connector Controls resolves a credential for each provider in 2 stages. It first
checks whether the provider has a credential supplied outside of Connector Controls,
and only then falls back to the managed assignment.

A non-empty environment variable for the provider — for example, `ANTHROPIC_API_KEY`
[added with `vip config envvar set`](https://docs.wpvip.com/infrastructure/environments/manage-environment-variables/)—
always takes precedence. If none is set, a non-empty PHP constant of the expected
name (`OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GOOGLE_API_KEY`) takes precedence 
next. Connector Controls never modifies an existing environment variable or redefines
an existing constant. Managed assignment applies only when neither exists.

Within the managed assignment, the most specific scope takes precedence: a network
site’s own assignment, then its environment’s, then the organization’s. Each scope
can be set to a specific credential, **Inherit broader assignment**, or **No managed
credential**. Setting a scope to **No managed credential** prevents any further 
inheritance.

| Scope checked, most specific first | Set to a specific credential | Set to “No managed credential” | Set to “Inherit broader assignment” | 
| Network site (multisite only) | That credential is used; resolution stops. | No credential is used; resolution stops. The environment and organization are not checked. | Resolution continues to the environment. | 
| Environment | That credential is used; resolution stops. | No credential is used; resolution stops. The organization is not checked. | Resolution continues to the organization. | 
| Organization | That credential is used. | No credential is used. | Not applicable. The organization has no broader scope to inherit from. |

## Activate Connector Controls for the organization

 1. Log in to the [VIP Dashboard](https://docs.wpvip.com/vip-dashboard/) and select
    the organization.
 2. In the organization view’s left navigation, select **Integrations**. This opens
    the [Org Integrations panel](https://docs.wpvip.com/integrations/org-integrations/).
 3. If Connector Controls isn’t listed yet, select **+ Add Integration** and add it
    from the [Integrations Center](https://docs.wpvip.com/integrations/center/).
 4. Next to Connector Controls, select **Manage**.
 5. Turn on **Activate Connector Controls**.

## Add a managed credential

Add credentials from the same panel used to activate Connector Controls: the **Manage
Integration** panel at the organization level or the [**Configure Integration** panel](https://docs.wpvip.com/integrations/app-integrations/configure-integration/)
for a specific environment.

 1. Under **Managed credentials**, select **Add credential**.
 2. Select the **Provider**: OpenAI, Anthropic, or Google.
 3. Enter a **Credential name** to identify it in assignment lists later.
 4. Enter the **API key**.
 5. Select **Add credential** to save it.

**Note**

Once saved, a credential’s key can’t be viewed again. It can only be rotated or 
removed.

## Assign a credential to a provider

 1. Under **Credential assignments**, find the row for the provider.
 2. Select a specific credential (listed by name and the scope that owns it), **Inherit
    broader assignment**, or **No managed credential**.
 3. Select **Save assignments**.

## Rotate or remove a credential

Next to the credential, select **Rotate** to replace its key or the trash icon to
remove it.

To rotate, enter the **New API key** and select **Save new key**. The credential
keeps its name and existing assignments; only the key value changes.

To remove, confirm **Remove credential**. Any assignment still pointing at that 
credential shows as unavailable until it’s reassigned and saved.

## Check the live credential source

Next to each provider, an info icon opens a runtime status panel showing what WordPress
is using for that connector, along with when that status was last observed. If an
environment variable or PHP constant is overriding a managed assignment, the icon
changes to a warning, and the panel notes that the override is in effect.

This reflects what the WordPress AI Client reports in the current environment, not
confirmation that the provider has accepted the key.

## Troubleshooting

### A provider isn’t using the organization’s shared credential

An environment variable or PHP constant defined in that environment’s code takes
precedence over any managed assignment. Open the runtime status panel for that provider
to see which source is actually supplying the credential. Remove or rename the environment
variable or constant in code if the managed credential should be used instead.

### The field on the Connectors screen is locked

While Connector Controls manages a provider, WP Admin’s **Connectors** screen keeps
that field read-only, even if the resolved value is no credential at all. This is
expected. Manage the credential from the **Integrations Center** in the VIP Dashboard
instead of the **Connectors** screen.

### An assignment shows as an unavailable credential

The credential a scope was assigned to has been removed. Open **Credential assignments**
for that scope and select a different credential, **Inherit broader assignment**,
or **No managed credential**. Then save.

### Credentials are saved but nothing happens

The environment is running a WordPress version earlier than 7.0, where the **Connectors**
screen doesn’t exist yet. Credentials and assignments are saved and will take effect
automatically once the environment is updated.

Last updated: November 10, 2026