> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/query/get-identity.md).

# Get identity

With the **Get identity** step, you can retrieve a user's full identity profile automatically when you run a workflow.

By leveraging automated collection of identity metadata, DoControl provides more sophisticated and accurate threat detection, allowing you to respond faster to any potential security incident.

{% hint style="success" %}
To leverage the **Get identity** step, you need to be connected to the Identities module with Google Workspace and HRIS/Okta.
{% endhint %}

Based on a user's email, identity metadata is retrieved from multiple sources and includes both personal data and risk exposure parameters, such as:

* Full name
* Job title
* Manager
* Job location
* Comprehensive work and personal email lists
* Comprehensive manager work and personal email lists
* Risk score
* DLP exposure
* Public, external and internal exposure summaries
* Departmental risk score

## **Use cases**

An employee in your organization is on the identity watchlist, and externally or publicly shares a sensitive asset. You can retrieve the user's current risk status using the **Get identity data** action to determine if the employee has behaved in other suspicious or potentially risky ways.

## **Retrieve identity metadata**

1. Select the relevant **App** and trigger.
2. From the Actions pane, select **Query** **> Get identity,** drag it to the canvas and connect it to the trigger.
3. Click the action to open its settings.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FtUTSL9aLPrCXMqFbRvWp%2FGet%20identity%20step.png?alt=media&amp;token=12c1a283-ae85-4859-9c62-0929bade8f70" alt=""><figcaption></figcaption></figure>
4. Add a step description (optional).
5. Define the action settings:<br>

   **Actor email** - Enter the user email for the actor, target or collaborator for whom you want to retrieve identity metadata. Or click the **Plus** ![](https://docs.docontrol.io/~gitbook/image?url=https%3A%2F%2F3236294211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MesrnyDMZGYg1V-tOBo%252Fuploads%252FMFokaiNx127HyZD93Ph3%252Fplus%2520icon%25202.png%3Falt%3Dmedia%26token%3D6bd9644a-ea2a-4969-81de-0a49a61b3dd7\&width=41\&dpr=4\&quality=100\&sign=bd567885\&sv=2) icon to add [dynamic values](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings#dynamic-data) to include details from the event. DoControl retrieves identity metadata for this specific user.

## Share identity metadata

As part of your automated workflows that retrieve identity metadata, this data can then be automatically conveyed to anyone in your organization via a **Notify in Slack** or **Notify by Email** step.

<div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F62saYlgWyss5vLbAb0Nf%2FNotify%20about%20identity.png?alt=media&amp;token=b5418438-0267-49c5-8737-9e4765836005" alt="" width="368"><figcaption></figcaption></figure></div>

Every workflow execution containing a **Get identity** step includes both personal and risk exposure data in a comprehensive output:

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fm2TwqBRxgLQz4fJcxQ5G%2FGet%20identity%20execution.png?alt=media&amp;token=7368ee10-b958-4b81-8335-c84e30a315d9" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Click **Export to CSV** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPWdaV30qx1aefHNdGX9C%2Fdownload%20icon.png?alt=media&amp;token=16257bf4-2b68-4417-91e6-78c5db741fdc" alt="" data-size="line"> to download a consolidated report of the identity metadata in CSV format.
{% endhint %}


---

# 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://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/query/get-identity.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.
