Connected apps

Open organization IntegrationsCopy Anchor Link

Select your organization, then open Integrations in its workspace. Developers use /console/integrations, utilities use /utility/integrations, and consultants use /consultant/integrations. The page shows saved access separately from whether you can use it now: an enabled service can still need a connection or be unavailable because access is suspended.

Reached-limit notices show a snapshot of API usage and screening budgets. They do not reserve capacity; the service checks the applicable budget again when you make a request.

Organization owners and admins can create API keys when the platform has enabled API access and self-service key creation. Save each new secret when it is shown; it cannot be displayed again. Existing API-key pages remain available. Members retain their existing personal connection permissions and cannot manage organization keys or installations.

Use the MCP setup instructions for the supported client and complete its credentials or sign-in flow. Enabling MCP does not connect a client automatically. Claude Desktop and Codex Desktop are the selected connection-testing targets; a setup screen alone does not prove live availability in either client. The public plugin's release and client approval requirements still apply.

Slack and Teams connections use your organization's existing feature permissions. Salesforce setup is utility-only and retains its separate release restrictions. If an action is unavailable, read its explanation before asking your organization administrator or support to enable it.

Connect the GridWonk pluginCopy Anchor Link

When the public GridWonk plugin is available in your client, install it and follow its sign-in flow. Use your own verified GridWonk account. The plugin may show Connection required after sign-in: open its secure setup link in your browser, sign in as the same person, and confirm the workspace you want it to use. Finish any required legal acceptance first. After you confirm, the page shows App connected. Confirmation links work once; reopening a used link does not reconnect the app. Manage or revoke the saved connection from Connected apps.

Return to the plugin and repeat your request. Completing setup enables that connection without requiring a different tool list. You do not need to paste an API key, token, or private repository path into a chat.

The connection is bound to the exact sign-in session and selected workspace. Switching the web app's workspace does not redirect an existing plugin connection. Each account has one active connection for this app. To select a different workspace, revoke the current connection, finish provider cleanup, then sign in through the plugin again and confirm a fresh connection. A second connection cannot replace an active one automatically.

What the plugin can doCopy Anchor Link

The plugin can research published requirements, prepare authorized developer drafts, attach supported packet files, start eligible reviews, and read status and cited results. Verified utility members can use the utility workflows their current role permits. Review availability also depends on supported utility coverage and processing allowances.

Document-role decisions, formal submission or resubmission, utility decisions, notice approval and sending, membership changes, and purchases require the website. The plugin cannot approve an application or change those permissions for you.

Review or revoke accessCopy Anchor Link

Open your connected applications from organization Integrations, or use Connected apps at /settings/connected-apps. Check the selected workspace and revoke a connection you no longer need. Local access stops immediately. If provider cleanup needs another attempt, follow the retry action before making a fresh connection. A revoked session cannot be reactivated.

If your membership expires, your role changes, or your account loses approval, the next plugin request uses that current access state. Reconnecting does not restore removed permissions. For an expired setup link, return to the plugin and request a new link. For a wrong-account message, use the account that signed in to the plugin.

If API or MCP access is disabled for the bound organization, subsequent MCP requests are refused, including requests from an already connected app. Disabling MCP alone does not disable permitted REST API calls. Enabling access again does not restore a revoked connection or expand your data permissions. You can still revoke your connection from the website while access is disabled.