> 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-profile.md).

# Get User Profile

## Description

The get\_user\_profile-parts provides functionality to copy the current logged on user details (name, email, roles, etc.) into your application context. Note that the method of authentication (local user, single sign on, etc) will impact what meta data is available for use.

## Use

By adding the get\_user\_profile-part into a process node the current user-details can be retrieved. This part can be used in combination with the show\_user-part and works independently from the project authentication configuration.

## Tips & Tricks

This part is most often used as part of LogicNets' Starter App Framework combined with an Assessment Framework application. Using this part in the Starter App will generate a container with information that can be used to populate a saved session table, e.g. record last modified by (You can choose from user\_email, first\_name, organization, etc.)

When a new (or resumed) session of the Assessment application is created, the LogicNets Starter App will post a string of the complete user profile across in the context, so it is available for use. As a Designer, you can choose to:

* \[most installations] use information in the Starter App user profile string in rules, routers, and other fields. You will need to place a *set data object* part in the onstart logicnet as follows (assumes user\_profile is the name assigned in the Starter)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f3d54b19f317e95fbc31b70c4fa3da4c90c0bd5c%2F6190498e-8210-409f-922b-c85a8a1bd100.png?alt=media)

* OR, \[only more sophisticated, multi-project applications] get the user profile from the Assessment Framework (that will potentially reveal different roles and user details)

## Editor Fields

| Field Name  | Description/Use                                                    | Type/Options | Optional/Mandatory |
| ----------- | ------------------------------------------------------------------ | ------------ | ------------------ |
| Data object | This is the path where the system stores the user profile details. | Data Object  | Mandatory          |

## Example

Download and import the following [example project](/release-9/example-gallery/example-projects-for-parts/get-user-profile-example-project.md) in your workspace.


---

# 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-profile.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.