Figma signs users in with their Figma account — the connector for design tooling, plugin companions, and anything that reads files or comments.

## Copy the redirect URI

In the [Authdog console](https://console.authdog.com), select the project and environment, open **Authentication > Providers**, find **Figma**, and click **Enable**. Copy the redirect URI shown in the form:

```url
https://identity.authdog.com/api/v1/callback/<connectionId>
```

## Create the application

1. Open [Figma's developer settings](https://www.figma.com/developers/apps) and create an app.
2. Name it and upload a logo.
3. Under **Callbacks**, add the redirect URI from Authdog.
4. Save, then copy the **Client ID** and **Client secret**.

## Configure Authdog

| Field | Value |
| --- | --- |
| **Client ID** | The client identifier from the provider |
| **Client Secret** | The client secret from the provider |

Save, then toggle the connection **active**.

## What Figma returns

Authdog requests the provider's default scopes and reads the profile from `https://api.figma.com/v1/me`.

The `/v1/me` endpoint returns the user id, email, handle, and avatar.

Figma returns the email on the account, and it is the address the person signs in to Figma with.

## Test it

1. Open your environment's hosted sign-in page, or link to `https://identity.authdog.com/api/v1/signin/<connectionId>`.
2. Select the Figma button and complete the flow.
3. Confirm the user appears under **Users** in the console with a Figma identity linked.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| `invalid_request` | The callback is not registered on the Figma app |
| Redirect or callback URL error | The URI registered with the provider does not match Authdog's exactly |
| Works in one environment only | Each environment has its own `connectionId`, and so its own redirect URI to register |

## Related

| Read | To learn how to |
| --- | --- |
| [Connectors](/docs/connectors) | Set up any other social provider |