Creating and Managing LabGroups (for System Admins)

The following information is only applicable to a Team or Enterprise instance of RSpace. In RSpace Community, anyone can designate themselves as a PI but in RSpace Team and Enterprise, PIs are created, revoked and assigned to LabGroups by the System Admin (sysadmin). The sysadmin can also change the PI for a given LabGroup and adjust the LabGroup membership as needed.

As System Admin, you have authority to create both PIs (Principal Investigators) and LabGroups.

PIs and LabGroups are closely connected:

  • While it is possible to create PI users without allocating them a LabGroup, they have no significant powers beyond any other user until they are connected to a LabGroup.
  • LabGroups cannot be created or exist without an allocated PI.

RSpace is flexible; You can either choose to create a new LabGroup at the same time as creating the user who is to be its PI, or you can choose to create the group later – and in more detail – and allocate an already-created PI user to manage it.

LabGroups can be used in a variety of ways. They can be permanent or transient to assist with management of things like short term projects. LabGroups may exist as a flat list with no overlapping members, or as more complex Venn diagrams or concentric, nested sets representing subgroups. Since data access is based on LabGroup membership, LabGroups can be organized to allow any complex data access schema required for your organization.

Creating a LabGroup when creating a PI user account

To create a new LabGroup during the creation of a new user account:

  1. Click on the System tab
  1. Click on Create account

  1. Choose PI as the role for the user
  1. You can then specify a name for the new group to be created, with this user as the PI. You can also optionally choose a community for the LabGroup.

This will cause both the PI user and their group to be added to the system. But, the new group will have no members except its PI, and it will be their responsibility to log on, open their group administration page and begin inviting other users to join the group.

Creating a LabGroup and assigning an existing PI user

Creating a group in this way will require the intended PI to already be registered as a user on the system and to have the role of PI.

To create a LabGroup:

  1. Click on the System tab
  1. Click on Groups

  1. Click on New LabGroup
  1. This will open the 'Create and configure a new LabGroup' form. You can give the group a name:
  1. You can then add a PI to the group, by searching for them in the left panel, and clicking on a checkbox:
  1. Then using the right arrow in the middle to assign them to this LabGroup.
  1. You can then select LabGroup members, from the pool of existing users; this step is optional, as LabGroup members can always be added later. You can search the list of available users using the searchbox on the left panel, select them using the checkboxes, and assign them to this group using the right arrow in the middle.
    1. You can also unassign specific or all users using the lower two arrows in between the panels.
    2. Clicking on a user opens their profile.
  1. Finally, click on Submit to create the LabGroup.

This initial membership and allocation of roles (such as making users LabAdmins) can then be managed by the PI when they log in and access the group’s page.

Changing the PI of a LabGroup

To change the PI within a group, the group must first have at least 2 members with the role of PI. If the group only has one member with the PI role, then that role must first be granted to at least one other memeber before the PI of the group can be changed by the sysadmin using the "change PI" button on the System > Groups > LabGroup page.

Dispanding a LabGroup

The sysadmin can dispand a LabGroup at any time by selecting the LabGroup in System > Groups and clicking "delete group". Note that no data is deleted when this option is used, but the shared data folder for the group is removed, and all previously shared data reverts to being accessible only to the owner of that data.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)