> 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/design-considerations-and-frameworks/user-management/configure-access-by-role/check-user-profile-at-runtime.md).

# Check User Profile at Runtime

With roles configured and users assigned to groups, you can check user roles when you start your application and display content or require actions based on those roles.

1\. To get a user's profile information in your application, add a process node and select Misc.

2\. Select *Get user profile* from the *Misc* dropdown menu. Using this part you can request information about the current user and save it as a data object.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7a34681ac6a737a0b4a1dbfc6c8a5e2a657de047%2F7083c5ba-d0bb-4589-9f9c-fe8a6fb3abed.png?alt=media)

3\. Enter a data object name for the user profile. This data object will contain a list of all roles assigned to the user in the location ‘roles\_collection’. All roles that are assigned to your user have the value 1; for example, 'user\_profile.roles\_collection.testers = 1'.

4\. You can use profile information in a rule node to determine the path the user takes or content the user sees based on that user's profile. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-053930d5742cabf7c02ee2339a69955b16a2bd9f%2F35789952-9cc7-4202-9a0b-0b1b8fe00efd.png?alt=media)


---

# 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/design-considerations-and-frameworks/user-management/configure-access-by-role/check-user-profile-at-runtime.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.