A group event registration portal can let one coordinator complete a roster of adult participants without giving them access to everyone attending the event. Store the group and its participant rows separately, show missing details by participant, and let event staff confirm the roster after review.

For fictional Harbor Design Forum, Cedar Studio plans to send six colleagues. Its coordinator needs to see which names and session preferences are missing, not repeatedly submit six unrelated forms. The event team needs a clear roster and a separate record of what it has actually confirmed.

Give the group a coordinator and each person a row

Use Coordinators with Name as primary text and Email as email. Events has Event name as text and Event date as a date. Groups has Group reference as text, Event and Coordinator as links, Organization name as text, Requested places as a number, Confirmed places as a number and Staff review state as a single select.

Participants has Participant reference as text, Group and Coordinator as links, Name as text, Email as email, Session preference as a single select and Coordinator note as long text. Add Staff completeness state as a single select, Staff question as long text and Registration outcome as a single select. These are proposed custom fields, not a prebuilt registration package.

Keep the direct Coordinator link on Participants as well as the Group link. The portal relationship is not inferred through the group. In this adult professional-event example, exclude medical details, identity documents and information about minors. Collect only the ordinary contact and event details the organizer actually needs.

Prepare a group-specific roster

For the first version, staff creates the Group and six Participant placeholders, each linked to the correct coordinator. Name them Cedar participant 1 through 6 until real details are supplied. The coordinator completes those prepared rows; they do not browse a global attendee table or link existing attendees from other organizations.

Create a miniExtensions Portal with Participants as the Data Table and Coordinator as the User Field. Follow the Users table instructions for the direct links. Add Groups separately through its Coordinator link if the coordinator needs to see the group-level review state.

Use the email verification setup for coordinator login. Configure each private view using the personal-record guide. In Portal Tables, select the table and view, then choose the personal-record display option under Filter and Sort. Check Groups and Participants independently.

Make missing information easy to resolve

Expose Name, Email, Session preference and an ordinary Coordinator note. Keep the Group and Coordinator links, Confirmed places and staff review fields outside coordinator editing. A useful view might show all six participants, with a second staff-prepared view for rows needing information.

The event team defines completeness explicitly. For example, a row needs a name, contact email and one valid session preference. Staff completeness state is a reviewed decision in this version, not an implied built-in validator. When something is missing, put a precise question beside that participant rather than a vague ‘Group incomplete’ message.

If the coordinator is still choosing the sixth participant, leave that placeholder incomplete. Do not invent a name or reuse another person’s email merely to satisfy a required field. Tell the coordinator whether a requested place is held under the event’s policy; the existence of a placeholder does not reserve capacity.

Review capacity and confirmations separately

Staff compares Requested places with the event’s actual capacity and policy before setting Confirmed places. If only four places are available, keep the six requested rows and clearly explain which four are confirmed and what happens to the remaining requests. Avoid making a general group status imply that every participant is admitted.

Session preferences are requests unless the organizer explicitly confirms allocation. This simple model does not prevent simultaneous overbooking or allocate seats atomically. Payment, ticket issuance, waitlist order and event entry remain separate processes unless you build and verify those integrations.

After reviewing the roster, staff records the outcome and communicates through its normal channel. A confirmation date or status field does not itself send an email. If an external ticketing system is authoritative, reconcile it before claiming the participants have active tickets.

Handle late roster changes without losing the original

Before confirmation, the coordinator may correct incomplete details in the allowed view. After confirmation, treat replacing a participant as a distinct request rather than overwriting the original person’s name. Preserve the previous roster and use the attendee substitution process, especially when tickets or allocations already exist.

Restrict reviewed rows using the record-editing guide and inspect all alternate views and creation/unlinking controls. Disabling expansion in one history view is not a guarantee that another route cannot change the same record.

If another employee becomes the group coordinator, staff verifies the change, updates the relevant direct links deliberately and tests both old and new access. Changing only the Group coordinator while leaving Participant coordinator links untouched can produce an inconsistent portal. Do not assume related records update themselves.

Test two groups before inviting real coordinators

Create Cedar Studio and another fictional organization with separate coordinators. Check that each sees only the intended group and participants, cannot change ownership links and cannot edit organizer decisions. Complete five of six rows, request an extra place and try a late replacement. Verify the saved relationships in Airtable after each step.

These are recommended checks, not runtime results. The workflow fits small professional events where a human coordinator gathers a team roster and organizers review the outcome. It is not a substitute for a ticketing platform with transactional capacity, payments or admission scanning. Its specific benefit is knowing which group’s details are missing and who is responsible for completing them.