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

# When is an integration enabled?

> Connecting an account is not the same as completing required User Settings. What each one unlocks.

Breadcrumb

It depends what you are asking. Connecting the account (signing in) is not the same as filling in required settings.

**Authentication** for an integration is done as soon as the user connects their account in the Connect Portal.

**Workflows**, including the [Integration Enabled](https://docs.useparagon.com/workflows/triggers/integration-enabled-trigger.md) trigger, wait until every **required** User Setting is filled in.

**The [Proxy API](https://docs.useparagon.com/apis/proxy.md)** can send requests immediately after authentication.

If you are seeing an integration marked as connected before a required field (for example a workspace or group ID) is set, that is expected. Workflows associated with those required fields fail as not enabled, but the user's authentication to the integration itself is complete.

## Details

| What you want to do | When it is allowed |
| - | - |
| User has a valid connected account | After they complete sign-in / OAuth in the Connect Portal |
| Run workflows, including Integration Enabled | After sign-in **and** all required User Settings are filled in |
| Send a Proxy request | After sign-in. Required User Settings are for workflows, not Proxy |

Required User Settings are the fields you mark required in **Customize Connect Portal > Configuration**. See [User Settings](https://docs.useparagon.com/connect-portal/workflow-user-settings). If a setting is not required, it does not gate workflows or Integration Enabled.

The Integration Enabled trigger is documented this way already: it fires when the user has connected an account **and** completed any required User Settings.

A successful Proxy call after Connect does not mean workflows are ready. A workflow that is not ready does not mean Proxy will fail.

## Related questions

* [User Settings](https://docs.useparagon.com/connect-portal/workflow-user-settings)
* [Integration Enabled Trigger](https://docs.useparagon.com/workflows/triggers/integration-enabled-trigger.md)
* [Proxy API](https://docs.useparagon.com/apis/proxy.md)
* [Headless Connect Portal (`enabled` on getUser)](https://docs.useparagon.com/connect-portal/headless-connect-portal)