> 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/user-attributes.md).
# User Attributes (BETA)
## Description
You can use the *user\_attributes* part to get additional information about a user who is currently logged onto the system. The LogicNets system stores standard user information, such as email or company, but it is also possible for you to set additional attributes. These include certifications or address information about a user. With this part, you can use an email address or user identifier to get information about any user on the system.
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 | | | |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
| Mode | Retrieve single attribute | Retrieve all attributes | Store single attribute | Store all attributes
This mode allows you to retrieve the attributes of a user defined by the category or store attributes. If you select to store, the system either makes a new entry to updates the entry of the user specified by the attribute category.
Default: read
| Dropdown | Optional |
| Attribute type | This is the category of the information that the system will update or get; for example, “certification” or “address”.
The value of the attribute type must be a string.
| Text | Mandatory | | | |
| Attribute key | When getting or updating a single attribute, you can define the attribute by this key.
This field is only visible when Mode is Retrieve single attribute or Store single attribute.
| Text | Mandatory | | | |
| Attribute value type | Text | Data object
When the attribute value is a data object and the mode is Store single attribute the system converts the data object to a string.
| Dropdown | Optional | | |
| Attribute value | This is the data object or string the system will update in the database. It is identified with an attribute key.
This field is only visible when Mode is Store attributes or Store single attribute.
| Text | Optional | | | |
| Attributes object | This is an object the system uses to update multiple user attributes with at once in the database.
This field is only visible when Mode is Store attributes.
| Data Object | Optional | | | |
| Result path | This is the output path to which the system saves the user attributes. | Data Object | Optional | | | |
| Error path | When an error occurs this data object will contain more information. | Data Object | Optional | | | |
| User email | Instead of the current user id this email will be used to identify the user.
The system hides this field when the company does not have an enhanced privileges license.
| Text | Optional | | | |
| Category | This is the package category.
This field is only visible if the company has an enhanced privileges license.
| Text | Optional | | | |
---
# 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/user-attributes.md?ask=&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.