Creating Communities (for System Admins)

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

Communities are ‘groups of groups’, reflecting higher levels of organisation within an institution, such as departments or schools. They are entirely optional, and for many smaller deployments you might never need to use them. They are mainly useful to help spread the admin load of the sysadmin, by enabling him to delegate to community administrators.Communities are only used to organise LabGroups. Collaboration groups may span across communities and are outside the scope of communities.

As a sysadmin user, you can view the list of communities by clicking on the ‘Communities’ button.

There is always a default community to which all new LabGroups belong by default, called ‘rs.default.allGroups’. To create a new community, click ‘New Community’:

sysAdminCreateCommunity

Each community needs to have an administrator – someone to manage groups and new users. The list of available administrators is shown in the bottom left panel. If there are no available admins, you’ll need to go back and create a new RSpace admin user account first ( go to ‘Create Account’ ). On the bottom-right panel is a list of LabGroups that you can add to this community. If you’re not sure which groups to add, you can edit this list later.

Once you’ve created a community, the admin is notified by email. The RSpaceAdmin will have similar powers to a sysadmin, but restricted to the users and groups within the community.

To subsequently edit a community, click on the link to that Community in the community list:

sysAdminEditCommunity

Here you can edit the community profile, move groups between communities, and add or remove community admins.


How did we do?