Manage reusable event fields and Events administrators

Tags: product:events intent:reusable-field intent:event-administrator intent:permission

Go to Events > Settings > Reusable Fields to manage event question definitions that can be reused across eligible event forms. Keep the reporting label and input type stable once a field is in use, and confirm which events use it before making a broad edit. Adding a reusable definition does not add it to every event automatically; select it from the event's Edit > Guest Information flow.

Go to Events > Administrators to add or edit event access. Assign the narrowest role that covers the person's work. An administrator may be able to view an event without being able to edit it or check guests in, and object groups can further limit which events appear.

General school or Online Giving administrator status does not automatically provide Events access. From School Dashboard > Administrators > [administrator], assign an Events-capable role and then review Events Access. Select All Events or grant the relevant individual events or event groups. Confirm both the role and the event scope when the Events menu or a particular event is missing.

Use the role that matches the required action. Current Events roles include Events Superadmin, Advanced Events Admin, Basic Events Admin, Events Content Manager, Events Communication Admin, Events Finance Admin, Events Reporting Admin, Events Check-in Admin, and Events View Only Admin. For example, Check-in Admin can check guests in and undo check-in but does not receive general event-editing access; View Only Admin can view an event but not its Edit Event area; Reporting roles cover applicable exports and reports; and refunding event payments requires Events Superadmin, Events Finance Admin, or school Superadmin permission. Managing other Events administrators is limited to Events Superadmin or school Superadmin. Because roles are permission bundles, confirm the exact action as well as the role name.

Preview the registration flow and run a test export after changing a reused field. Historical answers retain their record meaning, so changing a label does not rewrite past exports in every downstream system.