Version: 10.2

User Group Creation Based on Users

Introduction

Configure user-to-groups.map to create usergroups based on users.

warning

Apply the configurations shown in the Open iT Core Server.

Open user-to-groups.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

Notice that it contains instructions on how to edit the file.
Specify usernames with the following syntax:
Mapping Syntax
```
MAP: <UserGroupName> (<GroupType>)
<User1>
<User2>
<UserN>
```
note
It is recommended to include the GroupType, although the mapping will work regardless of its inclusion.

Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each user can belong to multiple groups.
Example
```
MAP: Finance (Department)
User079
User291
```
This example maps User079 and User291 in Finance and using the Department as group type.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

Open user-to-groups.map in the etc directory, which is by default in /var/opt/openit/etc.

Notice that it contains instructions on how to edit the file.
Specify usernames with the following syntax:
Mapping Syntax
```
MAP: <UserGroupName> (<GroupType>)
<User1>
<User2>
<UserN>
```
note
It is recommended to include the GroupType, although the mapping will work regardless of its inclusion.

Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each user can belong to multiple groups.
Example
```
MAP: Finance (Department)
User079
User291
```
This example maps User079 and User291 in Finance and using the Department as group type.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

This mapping may affect the following data types:

Licpoll2

Licenseevents2

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.

For real-time reports:

For historical reports: