Using systemli cloud as group

In our cloud, you find the Collectives app (to be found behind the star with »C« in the app menu on top). This app attempts to support activist and community projects with organizing.

In Collectives you can work collaboratively on documents, link them among each other and maintain templates for subpages - e.g. a template for meeting notes or for reflecting actions.

Ultimatively, the Collectives app combines the basic functions of a wiki (including full text search and backlinks) with a modern user interface and collaborative editing - as known from pads.

Furthermore, the Collectives app simplifies your user management. All admins of your collective can manage members in the Collectives app and add or remove accounts from it.

The documentation of Nextcloud Collectives can be found here.

If using the cloud as group, there's the problem which user the shared data (documents, calendars, deck boards, …) belong to. Therefore we strongly recommend to use Nextcloud Circles for groups:

• Each member of your group needs a personal systemli account.
• Additionally, you should create a group admin account that is maintained by several members.
• Create a collective (see above) for your group with your admin account. In your collective select “manage members” (in the three-dots menu of the startpage), add all the personal accounts. Feel free to grant admin permissions to some or all accounts.
• If you intend to use more functionalities of the cloud (e.g. folders for documents, calendars, Nextcloud Talk rooms, …), then create them with your admin account.
• Share all the additional resources for your group with the circle/team that has the name of your collective. That way, every member of your collective has has access to the other team resources.

If you follow the above workflow, you later can easily add/remove members from your group Circle. You don't have to share all objects again each time a new member joins your group. Also, you can spread the administration of your admin account among several team members and easily pass it on once the initial admins become inactive.