# Unlink someone from single sign-on

> Forget who someone is at the workspace's provider, so they (or another account there) link again on their next sign-in through it; their sessions go through it again.

<div class="g1t-endpoint"><span class="g1t-method" data-method="delete">DELETE</span><code>/workspaces/{workspace}/sso/identities/{username}</code></div>

Recorded as sso.identity_unlinked. Owners only, as people.

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`workspace`](/reference/mcp/#workspace) with `action` `unlink_sso_identity`, and the same inputs
- **Scope:** An access token needs [`access:admin`](/guides/authentication/#scopes).

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `workspace` | string | Yes | The workspace's name, e.g. "acme". |
| `username` | string | Yes | Whose link to forget. |

## Example request

```sh
curl -X DELETE https://api.g1t.sh/workspaces/flagon-io/sso/identities/ada \
  -H "Authorization: Bearer $G1T_TOKEN"
```

## Example response

A successful request answers `200` with:

```json
{
  "unlinked": true
}
```

## Errors

A failed request answers with one of these statuses and a body like `{"error": {"code": "not_found", "message": "Repository not found."}}`. See [errors](/reference/api/#errors).

| Status | Code | When |
| --- | --- | --- |
| 401 | `unauthenticated` | A token is required, or the one sent is not valid. |
| 403 | `forbidden` | The token is valid but not allowed to do this, such as a member-only change, or a token without the scope it needs. |
| 404 | `not_found` | It does not exist, or you cannot see it. |
| 409 | `conflict` | The request conflicts with the current state. |
| 422 | `invalid` | The input is not valid. `message` says which field and why. |