
A group is a name you attach to people and to the reservations they make.
It is how you answer "how much did that company actually do for us this year" without building a spreadsheet. Without groups, twelve people from the same employer are just twelve people. With a group, they are one partnership with a history. This article is for administrators.
The common thread is that the outside world thinks of them as one unit, and so should your reporting.
Once a reservation carries a group name, that name follows it everywhere the reservation appears:
That last one is the real argument for groups. A partnership you can only describe anecdotally is a partnership you will struggle to renew.
This is the most common confusion, and the names do not help.
You can run group reservations forever without ever creating a group. What you cannot do is total them up by organization afterwards, because without a group there is nothing to total by. Linking a reservation to a named group is what turns a series of separate bookings into a partnership history.
Three approaches, and the trade is always accuracy against effort:
Most organizations should start with both. Self-selection gets you coverage, and the ability to correct means the occasional "Acme" and "ACME Inc." duplication is fixable rather than permanent.
Tags on the group itself, not on people. They categorise types of group: Corporate Group, School Group, Faith Group, and so on.
The point is reporting one level up. Group tags let you answer "how much did our corporate partnerships contribute" across every company at once, rather than adding up twenty named groups by hand.
Worth distinguishing from profile tags, which sit on a person and gate what they can see. A group tag describes the group. It is a label for grouping your groups.
They can. Group is one of the six levels Vome can generate a chatroom for, and its membership stays synchronised with the group's current people.
It is off by default, and it is the natural way to talk to a partner organization as a unit rather than messaging their people individually.
Admin access is scoped by site, opportunity and profile tag rather than by group, so a group is a reporting and communication object rather than a permissions boundary.
If you need somebody to only ever see one partner's people, look at profile tags and admin scoping instead.
Ask what reporting you are asked for at the end of the year.
If anyone ever asks you how many hours a particular company, school or congregation contributed, you need groups, and you need them before the year starts rather than after. Group membership is not something you can reconstruct convincingly from memory in March.
If nobody asks that, and people arrive as individuals, groups are an Enterprise module you can genuinely skip.