> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-user-details-beta.md).

# Get User Details (BETA)

## Description

The *authentication.get\_user\_details* part retrieves user details about a user registered in the system by matching either an email address or user identifier id (GUID). The system returns the following details in the result:

* Id
* Firstname
* Middlename
* Lastname
* Company
* Settings
* Account expiry date
* Password expiry date
* Data
* Status
* Type
* Email
* Guid

NOTE: This part is currently in the Beta phase. You can only use this part if your company has enhanced privileges or a system package.

**Node Type:** This part is located in process nodes in the *Users* dropdown menu.

**Used With:** You can use this part with standalone and framework-based applications.

## Editor Fields

| Field Name      | Description/Use                                                                                                      | Type/Options | Optional/Mandatory |
| --------------- | -------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Identifier type | This allows you to determine if the system will find the user by an email address or by a user identifier id (GUID). | Dropdown     | Mandatory          |
| Identifier      | This is the identifier by which the system finds the user in the data model.                                         | Text         | Mandatory          |
| Data object     | This is the object in which the system saves the result.                                                             | Text         | Mandatory          |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-user-details-beta.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.