Group-first design means you decide who is in the room before you decide what the app shows. A partner meet has at least two audiences, the company’s partners and the company’s own staff, and they should not see the same content, the same polls or the same results. In Sociana a Group is a cohort inside an occasion that can scope content, polls, chat, notifications and leaderboards, so one app serves more than one audience instead of two apps serving one each.
One caution before we begin. Group scoping is configured and checked module by module. Some older group-related routes are not used by current apps, so we demonstrate scoping on the module you care about, whether feed, polls, notifications or chat, rather than assuming every feature obeys every group.
Why does a partner meet need groups at all?
Think about what happens when one broadcast reaches everyone. A reminder about a staff-only briefing lands on partner phones. A flight detail meant for travelling partners confuses employees who live in the city. A poll about channel incentives is answered by the very people it is about, and the answers mean nothing. Each of these is small, and together they teach guests to ignore notifications.
Groups fix the cause rather than the symptom. Every member belongs to a group, and the organiser picks a group when they create a poll or schedule a notification. Scheduled notifications can go to everyone or only to selected groups. Group polls restrict a question to one or more groups, with results reported per group.
How did a destination partner meet use groups?
The HCCB Partners Meet 2026 in Goa, in July 2026, is our clearest example. The app mapped every registered mobile number to Partners or Employees before launch. Each group then saw its own content and its own travel details. Overseas partners signed in with email instead of a mobile number. The event team, Managers and Owners, had attendance and notification tools on top.
The decisive step was the mapping itself. A number not mapped to any group saw only Home and Profile, with a message pointing to the helpdesk. That is the safe default: when the system does not know who you are, it shows you almost nothing, rather than showing you everything. You can read the full configuration in the HCCB case study.
What should you scope, and what should stay shared?
Not everything should be scoped. A rule of thumb we use:
| Content | Scope by group? | Why |
|---|---|---|
| Travel, flights and accommodation | Yes, per person | Different for each guest and sensitive |
| Agenda sessions for staff only | Yes | Partners do not need them |
| Awards, Reel and highlights | Usually shared | The shared moment is the point |
| Poll about partner incentives | Yes, partners only | Employees would distort the result |
| Venue map, emergency contacts, style guide | Shared | Everyone needs them |
| Unified leaderboard | Shared, with staff excluded | Honest results need staff off the board |
The last row matters. The unified leaderboard supports excluding staff accounts so internal team members never top a partner table. If a partner meet runs a games programme, decide before launch whether staff play at all, and whether they appear anywhere.
How do you map people to groups without a mess?
Groups come from an import, from a rule such as a zone or category, or, where enabled, from self-join. For a partner meet, the import is usually right. The steps look like this:
- Start from the source of truth. Usually the partner list from the channel team and the staff list from HR. Resolve duplicates before anything is loaded.
- Match identity carefully. The mobile number a partner registers with must be the one on the list. Decide in advance how you handle partners with two numbers.
- Assign groups on import. Partners, Employees, and any extra cohorts such as zones, categories or award finalists.
- Decide the unassigned experience. Home and Profile only is a sensible default. Make sure the message points to a human.
- Test with real numbers. Log in as a partner, as an employee, as an unmapped number and as an international guest, and confirm each sees what you intended.
Zones and categories matter in Indian channel structures. If your partner meet is organised by zone, think of each zone as a group, and let zonal leads see their own people. Our guide to dealer and partner meets covers the wider setup.
What are the failure modes?
Three come up repeatedly.
The orphan. Someone registers late or with a different number and sees nothing. Keep a visible route to the helpdesk and have a person watching the unassigned list on the day.
The leak. A notification or poll is created without choosing a group and goes to everyone. Make “Select Group” the working default for the team and treat “Send To All” as a deliberate choice.
The false assumption. The team assumes a module is group-aware because another one is. Test each module you rely on. This is the same caution as at the top of this post, and it is worth repeating because it is the mistake that costs the most.
How do groups change measurement?
Groups let you report per audience. Activation against invited partners and invited employees, separately. Poll participation by group. Hospitality completeness among guests needing travel. For HCCB these are exactly the denominators we plan to state when the client approves figures, and we do not quote them until then.
Reporting by group also protects you from a flattering average. A meet with strong employee participation and weak partner participation can look healthy in total. The partner number is the one the channel head cares about, so report it by itself. The definitions are in our glossary: participation rate and activation rate.
Frequently asked questions
Can one person be in more than one group? Group membership can be configured in more than one way, such as a role group and a zone group. Confirm the behaviour for the module you rely on before launch.
Is group-first the same as personalisation? No. Groups are cohorts that an organiser defines. Personal arrangements such as My Stay are per person and come from the hospitality workspace.
Is it cheaper than two apps? The HCCB documentation records the lesson that scoping by group is cheaper than running two apps, because content, branding and the engine are shared. Your own cost depends on the scope you agree.
If you are planning a partner meet, start with the guest list shape and we will propose the groups.