> 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/configure-users.md).

# Assigning Users to Roles

Once you have created roles and published your application, you can assign users to those roles either individually, or by group (steps below).

1\. From your LogicNets dashboard, click on the *Access Management* tile.

2. Go to *Groups*.

3\. Click *new* to create a new group.

4\. Give your group a name and click *Add*.

5\. Go to the *Assign new roles* section and select the application that you just published.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-832ee66c42056e9e9ecc22e5f4841130d5e03cae%2F829543f8-e7a9-4d50-ae84-d119dc3fa4ee.png?alt=media)

6\. The system will load in this section the roles you defined in your published package. Click on the role that you want to assign to this group and click *Assign*. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c57f0f91aaeb00a2722b58cc20a5ab6063c844eb%2Fc96e0141-b7a2-42fb-b0d6-0ad045d30039.png?alt=media)

7\. Once you have assigned a role name to your group you can add users to the group. In the *Group details* section select users by picking them from the *Users* dropdown list.

8\. Continue adding groups and assigning users to those groups, as necessary.

9\. Save all changes to your group by clicking *Save*.


---

# 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/configure-users.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.