These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Community Event Platform
- Features
- Community groups
Community groups
Keep venue and resource context clear for each event.
OverviewCompleted events×
Community Event Platform · Community groups
New
Completed events
Community events
| Record number | Name | Status | Event date | Completed at | Organization | |
|---|---|---|---|---|---|---|
| CE-39332 | Event 339 | Completed | 10 Oct | 13 Oct | ORG-8604 | |
| CE-81161 | Event 314 | Completed | 13 Oct | 15 Oct | ORG-3552 | |
| CE-18183 | Event 254 | Completed | 05 Oct | 10 Oct | ORG-4803 | |
| CE-28825 | Event 402 | Completed | 16 Oct | 15 Oct | ORG-2100 | |
| CE-30505 | Event 657 | Completed | 09 Oct | 12 Oct | ORG-2370 |
6 of 6 records
Event 339Community events · CE-39332
CompletedEvent date10 Oct
Completed at13 Oct
OrganizationORG-8604
What you can do
Keep the operating record clear
Community groups holds the setting used by an event. A group belongs to an organization and records a name, code, contact, address and eligibility note. The Event Owner selects that record when preparing an event, so the setting is visible from the event rather than buried in a separate message. The active flag helps staff distinguish a current choice from an older entry.
How the work is organized
- Maintain the setting. Admin or Event Owner checks the group contact and address before linking it to an event.
- Keep ownership aligned. The group and event must refer to the appropriate organization.
- Review the choice. The Event Owner checks the eligibility note and active state when presenting event scope for review.
What to agree during setup
Agree who maintains group names and codes, who can make a group inactive and what the eligibility note means for event planning. Confirm each group belongs to the right organization. Rehearse an event using an active group and another needing a different setting.
Check the handoff on an actual case
A neighborhood organization hosts a workshop in one of its community groups. The group record carries a contact, address and eligibility note. The event references that group, so the owner can check the setting before review. If the group is marked inactive, the team resolves the location choice before opening admission rather than assuming the old contact is still available.
For a second rehearsal, change the group contact after the event has been drafted. The Event Owner should inspect the selected group again before sending the event to review; the event still points to the same group record. If the chosen group belongs to a different organization, resolve the ownership mismatch before staff rely on its address or eligibility note. Keep the group code stable so imported events and current event records point to the intended setting. The Independent Reviewer can then read the group from the event while deciding the current event revision.
What your team sees
- Open event calendar — Open events by date; select one to inspect its group and capacity.
- Event review queue — Events awaiting review, with their linked group in the selected record.
Follow the work through
- Event approval connects the draft and reviewer decision.
- Registration to admission follows the participant request and capacity.
- Event closeout reconciles admission and provider evidence.
Check the record definitions before importing active work.
What it keeps track of
Data model- Community groups
- Physical or virtual venues and resource providers used by events.
- Community events
- Programs, events and sessions with capacity, lifecycle and revision.
- Organizations
- Operating organizations that own events, venues and team members.
Who uses it
Permissions- Event Owner
- Chooses the group for an event.
- Admin
- Maintains organization access.
- Independent Reviewer
- Reads the event setting when deciding the current scope.
Set up Community Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.