diff --git a/docs/user-documentation/general-admin-users/admins-documentation/multi-group-set-up.md b/docs/user-documentation/general-admin-users/admins-documentation/multi-group-set-up.md index 7a25591abc1ed8732775025ab46ede5bd6c54254..70c49ebb641a5ddc8894fcf7cd885e15b98c2070 100644 --- a/docs/user-documentation/general-admin-users/admins-documentation/multi-group-set-up.md +++ b/docs/user-documentation/general-admin-users/admins-documentation/multi-group-set-up.md @@ -1,5 +1,29 @@ Multi Group Set Up ==== + + +openBIS can be configured to be used by multiple groups, where every group only sees their own group Spaces. +This configuration needs to be done by a system admin, as described [here](https://openbis.readthedocs.io/en/latest/system-admin-documentation/advanced-features/share-ids.html). + + +In the example below we see two groups: RDM and ETHRDH. For each group, in the Inventory, there area n Equipment, a Materials, a Methods and a Publications Spaces with the group prefix. In the lab notebook, each group member has a personal Space where the name is the group prefix and the username of the user. + + + +It is possible to configure the user management configuration file (sys admin) not to create user Spaces for a given group, in case one group prefers to organise their notebook by project, rather than by group members, as described [here](https://openbis.readthedocs.io/en/latest/system-admin-documentation/advanced-features/share-ids.html). + + +In a multi group instance users are automatically registered and the roles defined in the user management configuration file on the server are automatically assigned to them. There is a maintenance task that runs in the background at a frequency determined by the system admin. This can be once per day or several times per day. If there are new users, they will be added to openBIS when the maintenance task runs. + + +An instance admin can assign additional roles to users from the admin interface ([User Registration](https://openbis.readthedocs.io/en/latest/user-documentation/general-admin-users/admins-documentation/user-registration.html)). Default roles defined in the user management configuration file and automatically assigned cannot be removed, because they will be assigned again automatically by openBIS when the maintenance task runs. + + +We would recommend to assign SPACE_USER rights for the Inventory Spaces to every group user and SPACE_ADMIN rights for their own lab notebook. This can be specified in the user management configuration file by the system admin. + + +In the user management configuration file, one or more admins for each group can be designated. The group admin has by default SPACE_ADMIN rights to all the Spaces of their group. A group admin can customise the [Group ELN Settings](https://openbis.readthedocs.io/en/latest/user-documentation/general-admin-users/admins-documentation/multi-group-set-up.html#group-eln-settings) for the group. + ## General ELN Settings diff --git a/docs/user-documentation/general-admin-users/admins-documentation/new-entity-type-registration.md b/docs/user-documentation/general-admin-users/admins-documentation/new-entity-type-registration.md index 55aec609ba8070c200afd6b6dbb60705f9a6952b..f38f5a24dcccb16d41f6d93626e1d8736bf7db1b 100644 --- a/docs/user-documentation/general-admin-users/admins-documentation/new-entity-type-registration.md +++ b/docs/user-documentation/general-admin-users/admins-documentation/new-entity-type-registration.md @@ -7,13 +7,11 @@ types, as well as *Property types* and *Controlled Vocabularies* constitute the openBIS **masterdata**. They can be created by someone with *Instance admin* role in the **new Admin openBIS UI**. - Note: *Material* types are also part of the openBIS masterdata. However, they are no longer supported and will be decommissioned soon. They should NOT be used. - The new Admin openBIS UI can be accessed via a URL of this type: **https://openbis-xxx/openbis/webapp/openbis-ng-ui/**