As the organization owner, if you set the permissions model to role-based, instead of repository-based, you can create your own roles and groups for users. You would set this on the General tab of the Oranization Settings page. This is described Oranization Settings page in this section of the Documentation.
Once you do that, you can begin to add users, add roles, and add groups. It’s not necessary to do them in that order, but since there is some logic to that order, the next few sections present them like this.
Users are added to an organization in Humio, under the Users and Permissions section. Just click on the Users tab to start. For a new account, you’ll see just one user, yourself. In the screenshot shown in Figure 1 here, you can see the organization owner and that an additional user was added.
To add more users, click on the + Add… button to start the process. A small dialog box will appear asking you to enter a user name. We recommend you use their organization email address. This will generate an email that will be sent to them, inviting them to join your Humio organization. It will also give them some basic instructions and links to log into Humio Cloud.
Once you add a user login name (i.e., the user’s email address), you can add some profile information in the right panel (see Figure 1), under Details. You would click Save to save any information you enter. Should you ever want to remove a user, you would do so under where it says, Danger Zone. It’s highlighted in the screenshot here. Under that same tab, you can promote a user to Organization Owner — you can have more than one, by the way.
You can assign a user to a particular group and give them permissions, or rather roles, under Groups & Permissions. However, you may want to add some roles and groups first.
To add roles, go to the Roles tab on the left. You’ll see a screen like the one shown in Figure 2 here. Click on + Add… to add a role. A small dialog box will ask you to name the role. After you do that, you’ll be able to set the permissions for the role. In the example shown in Figure 2, we named the role, Monitor. You may name your roles whatever makes sense for your situation. At a minimum, you would generally give a role Read Access to give users, to whom you assign the role, the ability to access the repositories.
In the example in the screenshot here, we gave the user that and all Search permissions, but nothing else. You may choose whatever permissions you want. If you find your choices are too restrictive, like our example in Figure 2, you can come back to this panel to change them later. When you’re finished setting the permissions for the role, click Save.
it-dept. This group will be for users who are part of the IT department of the organization. You can see it listed under the middle panel, along with the administrative one the system created automatically when first creating the organization. For that group, it has a prefix for the initial repository. That’s because when the organization was created, it was set to use repository-based permissions, the default. Now that the permissions model has been changed to role-based, we don’t need to use that pattern of naming groups: it no longer applies or makes sense since groups can now apply to multiple repositories.
Incidentally, groups may be renamed or deleted under the Danger Zone tab in the third panel for a particular group.
You may have noticed in the third panel of the screen shown in Figure 3, that it shows the tab labeled, Repositories and Views. Here you can add the repositories the users of the group have permisssion to access. You would just click on + Add Repository or View to give permission for either a respository or a view.
Since the example used for this documentation page is of a new organization, there’s only one repository so far. Notice also that we’ve set a role for this group in relation to the repository, the Monitor role. You can give a group more than one role, if that would be appropriate.
Notice that for the example we’ve already added some more users to the organization. To add some of them to the group, click on + Add…. You’ll then see a pull-down menu, as seen in Figure 4, labeled, Add User by Name. It will show you a list of users that are not already assigned to the group. Just select the ones you want to add.
Later, if you want to add another user to the group, perhaps a new user, you can return to this screen to add them. However, you can instead go to the User tab on the left and then to the Groups & Permissions section for that user. Both work as well for adding a single user, but from the User tab you can see more clearly what a particular user has permission to do. This can be useful when you have multiple repositories, multiple roles, and multiple groups and many users.