> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Sample Flows

## Article: Sample Flows

## Article Link: https://dev.wix.com/docs/api-reference/business-management/headless/connections/sample-flows.md

## Article Content:

# IAM Connections: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

## Temporarily disable authentication methods

During maintenance or security incidents, you need to temporarily disable a specific authentication method without losing its configuration. This allows you to quickly reactivate it later.

To temporarily disable a Facebook authentication connection:

1. Call [Disable Connection](https://dev.wix.com/docs/api-reference/wix-backoffice/identity/connection-v1/disable-connection.md) with the Facebook connection's ID. The Facebook sign-in option is immediately removed from the site's login page, while the connection configuration remains intact for future reactivation.

## Retrieve connection data for client applications

Your frontend application needs to display available sign-in options to users. The client data endpoint provides only the information safe for client-side use.

To get connection information for a login page:

1. Call [List Enabled Connections Client Data](https://dev.wix.com/docs/api-reference/wix-backoffice/identity/connection-v1/list-enabled-connections-client-data.md) from your frontend application.

2. The response contains only client-safe fields — the connection's ID, its app definition ID, and a display name:
   ```json
   {
     "connections": [
       {
         "id": "2f3c8a1e-0b7d-4e2a-9c11-8a1e0b7d4e2a",
         "appDefId": "1380b703-ce81-ff05-f115-39571d94dfcd",
         "displayName": "Continue with Google"
       }
     ]
   }
   ```

3. Use this data to render sign-in buttons on your login page.

4. When users click a sign-in option, redirect them to the appropriate authentication flow using the connection information.