> 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/managing-users/assigning-framework-logicnets-packages-to-user-groups.md).

# Assigning Framework LogicNets Packages to User Groups

A number of LogicNets framework packages provide basic building blocks for application management, including User Management and System Configuration. These packages allow you to designate roles and assign groups to those roles.

To implement and assign user access based on group do the following from the *Access Management* package on your LogicNets dashboard:

* **Step 1**: Go to *Groups* on the navigation menu and select a group to which you want to assign a role/privileges. Click ***Modify***. Select the package you want to assign from the *Packages on dashboard* dropdown menu.
* **Step 2**: In the *Group roles* section, add the appropriate roles by selecting the package you added and assigning a role. If you want to add more than one role, you will need to add a line for each one; see the table below.

To remove/change a group role, click on the red delete button at the end of the line; see 3 in the screenshot above.

The following table identifies the packages and associated roles available.

| Package                  | Required Role                                        | Notes                                                                                                                                                                                                     |
| ------------------------ | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| User Management          | (multiple)                                           | See [Assigning User/Access Management to Admins](/release-9/design-considerations-and-frameworks/user-management/managing-users/assigning-useraccess-management-roles-to-groups.md) for more information. |
| Deployment Manager       | admin                                                | See [Deployment Manager articles](/release-9/platform-documentation/system-administration/deployment-manager/introduction-to-the-deployment-manager.md) for more information.                             |
| KnowledgeCenterApp       | <p>guest<br>user<br>publish<br>admin</p>             |                                                                                                                                                                                                           |
| oauth-tester             | admin                                                |                                                                                                                                                                                                           |
| Package Installer        | admin                                                |                                                                                                                                                                                                           |
| Scheduler Monitor        |                                                      | No roles defined/required.                                                                                                                                                                                |
| Standard Reporting       |                                                      | No roles defined/required.                                                                                                                                                                                |
| SystemConfiguration      | admin                                                | See [System Configuration](/release-9/platform-documentation/system-administration/system-settings.md) articles for more information.                                                                     |
| Test Framework API       | <p>create<br>manage<br>execute<br>view<br>system</p> |                                                                                                                                                                                                           |
| Test Manager             | manager                                              | See [Test Manager](/release-9/platform-documentation/test-manager.md) articles for more information.                                                                                                      |
| Web Services Framework   |                                                      | No roles defined/required.                                                                                                                                                                                |
| AssessmentFrameworkFhirQ | <p>api<br>addcase<br>sendfeedback</p>                | See [FhirQ Support](/release-9/platform-documentation/fhir-support.md) articles for more information.                                                                                                     |


---

# 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/managing-users/assigning-framework-logicnets-packages-to-user-groups.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.