> 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/hris-get-user-metadata.md).

# HRIS: Get user metadata

You can retrieve metadata of users from HRIS (human resources information systems) that are integrated with DoControl, including:

* BambooHR
* Deel HR
* HiBob
* Workday
* SAP SuccessFactors

User metadata can include the name and email of the employee's manager, the employee's group, and employment status.

#### **Use case 1**:

If an employee in your organization changes user access for a Google Drive asset so it's now publicly shared, you can choose to remove the public sharing if the employee fulfills certain criteria. You can use the **Get user metadata** action to determine if the employee is about to leave or has been terminated, or define a condition based on the actor's role, such as Vice President.

#### Use case 2:

If an employee in your organization externally shares a Google Drive asset using their private email, you can remove the sharing permissions from the asset. You can use the **Get user metadata** action to verify if one of the collaborators is the employee's private email.

#### To retrieve user metadata from HRIS apps:

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

   <br>

   <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%2FzCO7fXqdSqAfKtm6Q49T%2FHRIS%20get%20user%20metadata.png?alt=media&amp;token=4f6ecde1-b750-4359-a5d2-29df3a544253" alt="" width="563"><figcaption></figcaption></figure></div>
4. Add a step description (optional).
5. Define the action settings:
   * **HRIS app -** If a single HRIS is connected, the HRIS is automatically populated. If you're connected to more than one HRIS, select the relevant app, such as BambooHR, Deel HR, HiBob, SAP SuccessFactors, or Workday.
   * **User email** - Enter the user email for the actor, target or collaborator for whom you want to retrieve HR metadata. Or click the **Plus**  <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FMFokaiNx127HyZD93Ph3%2Fplus%20icon%202.png?alt=media&amp;token=6bd9644a-ea2a-4969-81de-0a49a61b3dd7" alt="" data-size="line"> icon to add [dynamic values](/docontrol-user-guide/workflows/define-workflow-settings/action-settings.md#dynamic-data) to include details from the event. DoControl retrieves HRIS metadata for this specific user.


---

# 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/hris-get-user-metadata.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.
