Skip to content
LogScale Self-Hosted
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

### Assign Roles to Groups

##### Security Requirements and Controls

- `Manage users` permission

Assign roles and permissions to groups within a security authorization system, including the process of adding users to groups and setting default permissions for repositories and views. The query prefix functionality allows administrators to filter search results for group members based on specific criteria like host names or other log attributes.

Once you have created a group you need to assign users to it, then assign permissions.

Any user who is assigned the `Change user access` permission (see Figure 112, “Change User Access”) can assign permissions to groups for a repository. Groups can also be assigned permissions from the `Groups` page by an organization owner or root.

### Note

If you intend on administering access to repositories and views centrally by an organization owner or root only be sure not to give out the `Change user access` permission to anyone. In practice this means removing the permission from all roles thus not allowing any users to go to a repository or view and add another user or group directly.

If you aren't keen on administering groups and roles as new repositories are created you have the chance of defining default permissions for a group here as well).

1. Go to Users and permissions → `Groups` and select your group from a list of available groups. You can search if the ones you are looking for are not immediately visible in the list.

2. To assign users to the group, go to the Users tab, click + Add... and select a user from the dropdown, then click Save:

   Figure 106. Assigning Users to Groups

   The user is now added under the `Users` tab for that group.

3. To assign default permissions to the group click the Permissions tab, click the cog icon to assign the default permissions of a role to all repositories and views or to individual ones, then click Apply.

   Figure 107. Assigning Default Permissions to Groups

4. In the Query prefix area, you can define a query prefix which is effectively a search filter applied to any search.

   Figure 108. Query prefix

   For example, you may add a query prefix `host=web*` for the group. This is a LogScale query that acts as a filter when any member of the group searches the repository developer. In effect a user of the group is only allowed to see log lines that have a host field that starts with `web`. E.g. `web-server01`, `web-server02` and so on. This allows partitioning of data at search time.

   ### Note

   Query prefix only accepts Query Filters whereas Query Functions are not allowed.

   It's also possible to define a default query prefix if a default role has been selected. Meaning the default query prefix will be applied to all searches in all repositories unless an exception is defined.

To assign a group to a role through your own application, use the assignRoleToGroup() mutation of the GraphQL API. To unassigned a roll from a group, use unassignRoleFromGroup().

#### Enter search term