Creating Groups (for System Admins)

The following information is only applicable to an Enterprise instance of RSpace.

As System Admin, you have sole authority to create both PIs and LabGroups, when instructed by your institution, or requested by PIs who want to have an RSpace LabGroup on your system. The Lab Group and the PI are the two interdependent parts of the basic functional administrative unit in RSpace. You should think of the two as completely connected: while it is possible to create PI users without allocating them a LabGroup at the point they are created, they have no significant powers beyond any other user until they are connected to a group. Groups, though, cannot be created or exist without an allocated PI.

So, 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.

To create a new LabGroup during the creation of a new user account: choose PI as the role for the user, and in the role-specific section under the basic details, specify a name for the new group to be created with the user as PI. 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.

newGroupAdmin

Creating a group as a stand-alone operation will require the intended PI to already be registered as a user on the system and to have the role status of PI.

In the System tab, open the Groups section to show a listing of the current groups on the system. Above the list of groups at the top left is a ‘New LabGroup’ button. Click this button to open the ‘Create and configure a new LabGroup’ form. In this form, you can again define an identifying name for the new LabGroup, but you now have the capability to add any number of existing users to the group as initial members. One of these initial members must be the user who is to be PI, and they should also be specifically identified as group PI in the later part of the form. Users who are added to the membership of the group can also be given Lab Admin status at this point, if this is known and required, then the group can be created.

This initial membership and allocation of roles can then be managed by the PI when they log in and access the group’s page.  But, it is possible using this method to create a LabGroup with a membership and role structure exactly to a PI’s specification or in reflection of the roles existing in an actual lab, which the PI and members can then log into and not need to edit or change.


How did we do?