
A group is a named record for an organization that volunteers with you: a company, a school, a congregation, a family. You attach people to it, you attach reservations to it, and from then on the partnership has a history you can total.
This article is a tour of the module itself. It covers creating a group, what lives on a group's dashboard, group tags, and the housekeeping tools you need once you have more than a handful of groups. This article is for administrators.
No, and this is the most common mix-up.
You can run group reservations forever without creating a single group. What you cannot do is add them up by organization afterwards, because without a group there is nothing to add them up by. See Group reservation policies: every setting explained for the reservation side.
Go to Groups in the left-hand navigation and click + New group.
The create popup asks for three things:
Click Create group and the group exists. Everything else, including the logo and cover photo, is added afterwards from the group's own dashboard.
Groups can also be created by a user during a reservation, if you allow it in the group reservation policy. That is covered in section 6 of the policy article.
Click any group card to open its dashboard. There are five tabs.
Members, Guests and the reporting tabs are covered in their own articles, linked at the bottom of this page.
Each setting is its own card:
Changes are not live until you click Save changes. Delete group sits on the same row, so take care.
Group tags are labels on the group itself, not on people. They describe what kind of group it is: Corporate Group, School Group, Faith Group, Family, and so on.
The point of them is reporting one level up. A group tag lets you answer "how much did our corporate partnerships contribute this year" in one query, instead of adding up twenty named companies by hand.
To manage them, use Manage group tags from the Groups module. You can create, rename and delete tags there. To put tags on a group, use Assign group tags from the group card's three-dot menu, or the Group tags card on the Details tab.
Worth keeping straight: a profile tag sits on a person and can gate what they see. A group tag sits on a group and is purely descriptive. They are different systems and they do not interact.
The left-hand panel of the Groups module gives you several ways to cut the list:
Yes. Select the cards you want, or use Select all, and you can:
For a single group, the three-dot menu on its card carries the same actions plus Edit group, which drops you straight onto the Details tab.
It can. Turn on the chat option in the Communication card on the Details tab, and Vome creates a chatroom whose membership stays synchronised with the group's current members. You can also make it announcement-only, so administrators post and members read.
It is off by default. It is the natural way to talk to a partner organization as a unit rather than messaging their people one at a time.
The group record goes, and it cannot be undone. The people do not go anywhere: their profiles stay in your database exactly as they were, they simply stop being members of anything.
Be aware that reservations linked to that group lose the link, which means the historical reporting you built the group for goes with it. If your only problem is that a group is no longer active, leaving it in place costs you nothing and keeps the history.
No. Administrator access is scoped by site, opportunity and profile tag, not by group. A group is a reporting and communication object, not a permissions boundary.
If you need somebody to only ever see one partner's people, look at profile tags and admin scoping instead.