> 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/roles-and-user-access-overview.md).

# Roles and User Access Overview

**Description** Establishing and configuring user roles allows you to better manage user access to your application or parts of your application. The following steps detail how to configure your project and users and how to make use of user profiles when running your application.

**Initial Installation** On the initial installation of LogicNets, the **admin user** [*admin@logicnets.com*](mailto:admin@logicnets.com) is created. This user is placed in a group called ***admins***. An additional group called ***users*** is also created. These entities should not be removed, but **will** be restored on any subsequent installation if they are removed at any time.

**Default Groups** The admin group is automatically approved for access to a variety of administrative packages, including User Management, and SystemConfiguration, as shown in the example screenshot below. For smaller organizations where the administrative functions of User Management, System Configuration etc. are managed by a single user, you can simply add that user to the admin group to give them access to these functions.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4235ced52ff3ea4e808831a7165bc0a90934c463%2Fc113d2dc-ccc3-4eaa-a29d-45298c313f5b.png?alt=media)

**Custom Groups** For larger or bespoke organization of roles and responsibilities, you can create your own groups and assign packages/roles to them, according to the designated division of responsibilities. See [Configure your Users](/release-9/design-considerations-and-frameworks/user-management/configure-access-by-role/configure-users.md) Support Article for more information on how to create a group, add packages and choose roles.

**Upgrading to LogicNets Version 7.3** If you are upgrading from an earlier version to LogicNets Version 7.3 where the role profiles for system packages has been introduced, you will find that after the upgrade, users (other than <admin@logicnets.com>) will no longer be able to access certain system packages, until they have been given the role profile in Access Management, EVEN THOUGH those users will show they have the appropriate package attached to their profile or their group.

Note that this scenario also applies to the Knowledge Center application. The speciifc step needed to resume access for these accounts is to do either of the following:

* add the user(s) to the admins group so that they are allocated the KC admin role
* for each user, click MODIFY and go to the Assign New Roles section, find the Knowledge Center App in the list and assign the admin role (see screenshot below)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f938ffc1a70c8b67c9e61152d071dc23e1892c2e%2F49930ff2-20a6-4433-9a81-a2e8696eba0b.png?alt=media)

\[Note that the Knowledge Center has the option to create and assign different roles aswell - admin, guest, publisher, user. For more information on how to use this functionality, see Support Article Knowledge Center Roles and Permissions.]


---

# 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/roles-and-user-access-overview.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.