> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/embedded-client-authentication-user-guide/configuration/use-embedded-client-authentication.md).

# Use Embedded Client Authentication

Follow the steps below to authenticate your customers securely using Clickatell's Embedded Client Authentication.

In both cases, a link is sent to the customer that they must use to authenticate themselves against your chosen identity provider. This navigates to a login page, where the customer enters their credentials to authenticate.

Once you've [configured](/embedded-client-authentication-user-guide/configuration/configure-and-update-an-identity-provider-idp.md) your identity provider (IDP), you can use the functionality on our Chat Flow and/or Chat Desk applications.

{% hint style="info" %}
All the IDPs you've set up in the Clickatell Portal will automatically pull through to your Chat Flow and Chat Desk applications.
{% endhint %}

## **Use OAuth in Chat Flow**

1. [Configure identity providers](/embedded-client-authentication-user-guide/configuration/configure-and-update-an-identity-provider-idp.md) in the Clickatell Portal.
2. [Set up the *OAuth Request* node](https://help.clickatell.com/chat-flow/user-facing-nodes/input-nodes/oauth-request#sending-a-payment-request-via-chat-flow) in your Chat Flow workflow(s) to authenticate customers.

## **Use OAuth in Chat Desk**

1. [Configure identity providers.](/embedded-client-authentication-user-guide/configuration/configure-and-update-an-identity-provider-idp.md)
2. [Use the OAuth extension](https://help.clickatell.com/chat-desk/agent-desk/authenticate-customers#use-the-oauth-extension) in Chat Desk to authenticate end-users.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.clickatell.com/embedded-client-authentication-user-guide/configuration/use-embedded-client-authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.