> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/identities.md).

# Connected identities

A connected identity maps a Distro member to their identity in another tool. Workflows use it to translate an assigned teammate into a CRM owner, Slack user or sequencing sender.

## Add a mapping

1. Connect the provider to the workspace.
2. Open **Members → Identities** or the member's connected-identity controls.
3. Select the Distro member and provider.
4. Enter or select the provider's actual user, owner or mailbox identity.
5. Save and validate a workflow that uses that member.

For HubSpot, use the owner identity needed by the operation. For Salesforce, use the Salesforce User identity. A Slack mapping belongs to the connected Slack workspace. Sequencing tools can require a mailbox or sender identity rather than a contact ID.

## Use the mapping

Select an earlier Distro owner or assignee in the workflow's supported picker. Distro then uses the mapping for that provider. Do not substitute a CRM record ID for a user ID.

For an SDR-to-AE handoff, the Distro assignee might be the AE while the sequencing sender is a specific mailbox. Decide which identity your action should use rather than assuming the person who connected the integration is always the sender.

## When a mapping stops working

Check the provider account, whether the user still exists and whether their mailbox or permissions changed. Reconnect and update affected steps after replacing the workspace connection.

See [CRM connections](/data-and-integrations/crm.md) and [Sequencing setup](/workflows/sequence-outcomes.md).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.distro.so/settings/identities.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 `build a script that syncs our docs to a CMS` 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.