# Choose an app's connectors

An app's **Parameters** section lists the connector slots its template declares. These choices control which providers the app's workflows use. They do not grant new connection permissions to you or other users.

## Understand the slot types

- **Required:** enabled and locked because the app needs the provider. The form does not let you disable or replace that slot.
- **Optional managed:** switch it on or off. Strive supplies the managed connection when needed.
- **Optional user-supplied:** switch it on and select an existing connection for the specified provider. Use **Create connection** if a suitable connection is not available.

## Enable a provider

1. Open the app's **Parameters** section.
2. Find the optional provider and enable its switch.
3. For a user-supplied provider, choose the connection you want the app to use. Ensure it belongs to the available tenant and matches the provider.
4. Complete any external authorization or connection setup.
5. Choose **Save changes**. Connector policy and editable parameters save together.

Enabling a user-supplied slot without selecting a connection is blocked. The error names the provider and asks you to pick a connection or switch it off. A connection for another provider cannot satisfy the slot merely because its display name looks suitable.

## Disable without deleting

Switching a provider off prevents the app's conditional workflow steps from using it on subsequent runs. Those steps are skipped rather than attempting to fetch credentials. The connection selection remains stored, so you can enable the provider again without rebinding it. Disabling the slot neither deletes the connection nor removes a signed-in member's access to it elsewhere in Strive.

The **Connections** workspace view may continue to list the connection because the workflows still reference it; an **Off for this app** marker explains the difference and links back to Parameters.

If saving fails, keep the displayed error and correct the selection or setup. A parameter conflict requires reloading and reviewing the current policy before reapplying your changes. For the connection's own authentication, health, and data controls, see [Connections](/docs/connections/overview).