6. User groups
In order to ensure flexibility in the handling of freely configurable workflows and the corresponding users, you will need to define a number of user groups. These user groups can be understood as the roles, activities or skills of individual users within the workflow. By way of example, user groups can be created for scan operators, metadata editors and administrators. You are free to define these groups as you wish in Goobi and then assign individual users to them. To open the list of existing user groups, click on the menu item
Administration - User groups in the menu. Goobi will display a list of all the user groups that have already been defined. For each of these user groups, you can also display a list of all the users assigned to that group. To show this list, simply click on the little symbol to the left of the user group name.List of all previously configured user groups and assigned users
To create additional user groups, click on the Create new user group link. To edit existing user groups, however, you need to click on the Edit symbol in the Actions column.
Icon | Description |
| Create new user group |
| Edit existing user group |
Within the editing mask, a title must always be assigned to a user group. This can be freely selected. Please make sure that you select this title as descriptively as possible to give you and other administrators in Goobi a better overview.
Editing a user group
Very granular permissions can now be assigned to each defined user group. These can be added in the right area of the form by simply clicking on an authorization. A click on an authorization in the left area removes it from the user group.
The following authorizations are available for selection:
This permission allows the user to view and use menu items in the Administration menu.
This permission allows access to the administrative area, in which a message can be sent to all logged in users.
This authorization allows you to list and edit dockets.
This permission allows you to list and edit LDAP groups.
This authorization allows the execution of administration plug-ins, as long as they are installed and do not require special individual rights.
This authorization allows you to list and edit projects.
This authorization allows you to list and edit rulesets.
This authorization allows you to list and edit user groups and their authorizations.
This authorization allows you to list and edit users.
This authorisation allows you to switch to the user account of another Goobi user without having to use their login data. A precondition for this is, however, that the User authorization and the Administration menu are also available.
This authorization allows you to display information on how many users are currently actively working in Goobi.
This authorization allows you to display the number of active users in Goobi as well as a detailed list of exactly which users are involved and when they last showed activity.
With this permission the user has the possibility to delete files that have been uploaded for a process within the process log or in one of the directories
import/, export/ or source/.Users with this permission can configure for which status changes they want to be notified. Within the user settings of each user, there are fields available that define the notification for status changes by mail. A notification is possible for the status change of tasks in the following cases:
- When tasks are ready for editing
- When tasks are accepted for processing by a user
- When tasks have been completed
- When tasks reach an error status
This permission allows the user to view statistics and use menu items in the menu.
This authorization guarantees access to the standard statistics available within Goobi.
This authorization allows additionally installed statistics plug-ins to be called.
This permission allows the user of the My Tasks menu to view and work with My Tasks.
This permission allows you to view and work with the user's own task list.
This authorization determines whether users with access to the internal metadata editor are allowed to work with the Pagination area.
This authorization determines whether users with access to the internal metadata editor are allowed to work with the Structure Data area.
This authorization determines whether users with access to the internal metadata editor are allowed to work with the Metadata area.
This authorization determines whether users with access to the internal metadata editor are allowed to work with the Files area.
This permission allows the user to see and use menu items in the Workflow menu.
This authorization controls whether the user may use the search mask to search for processes.
This authorization determines whether a user may also see processes in which he himself is not a member.
This authorization determines whether the user may group processes into batches or modify existing batches.
This permission determines whether a user is allowed to see the details of a process.
This permission determines whether a user can see and edit the details of a process.
This authorization allows additionally installed workflow plug-ins to be called.
This authorization controls whether a user has access to the list of process templates.
This authorization determines whether a user may clone an existing process template in order to create a new process template.
This authorization determines whether a user can create new process templates.
This authorization enables the user to create new processes individually on the basis of existing process templates.
This authorization enables the user to create new operations on the basis of existing process templates by carrying out a mass import.
With this authorization, the user has the option of having processes listed.
With this authorization, the user has the option of subsequently changing the process template to be used for an existing process.
With this authorization, the user has the option of downloading process information as an XML file.
With this authorization the user is able to perform a tabular export of a process list.
This authorization can be used to determine whether a user may create a link to the data in his home directory for a desired process.
This permission can be used to determine whether a user can also see processes from deactivated projects.
This authorization can be used to specify whether a user is to be given access to finished processes.
This permission gives the user the rights to apply all GoobiScripts over a number of operations.
It is possible for user groups to be given specific rights to execute selected GoobiScripts. For this purpose, the assignment of the permission is not done by clicking on one of the indicated rights in the right area. Instead, the GoobiScript to be allowed is named in the right input field and is accepted by clicking on the button with the plus icon. The assignment of the permission is done in such a way that
goobiscript_ is entered followed by the name of the concrete GoobiScript.Assign a permission for a GoobiScript
Accordingly, the following authorizations can be assigned as examples:
Name of GoobiScript | Assigning the GoobiScript as a permission |
addStep | goobiscript_addStep |
metadataChangeValue | goobiscript_metadataChangeValue |
setTaskProperty | goobiscript_setTaskProperty |
Last modified 1yr ago