> 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-users-and-packages-to-groups.md).

# Assigning Users and Packages to Groups

Groups allow you to simplify the management of user access to specific packages and roles. In Access Management you can create a group, specify what users who belong to that group can see and do in the system, and then assign users to that group.

In Release 7.3 and earlier, packages/roles can be assigned to a user directly, but current and future Releases manage this via group functionality, in line with user management best practices.

### Create a Group

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. Add users to the group. In the *Group details* section select users by picking them from the *Users* dropdown list.
6. Add any published packages that members of this group are authorized to access.
7. (Optional Step) Add any workspaces (Designer accounts) that members of this group are authorized to access.
8. Click *Save* to save your changes to this group.

### Link Users to Groups

There are multiple ways to link a user to a group:

1. Modify an existing group and add users to the group from the *Local Users* dropdown menu.
2. While creating a new user, assign the user to one or more existing groups using the *Groups* dropdown menu.

### Single User Assignment

See the article Assigning Packages to Users - Differences in Release 7.3 vs Release 7.4 for information about single user assignments and the Release 7.4 switch to managing users by group.


---

# 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-users-and-packages-to-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.