إنتقل إلى المحتوى الرئيسي

Organization events

/organizations/:id/events covers event lifecycle management for the active organization. In the CRM context, events connect contacts, participants, invitations, ticketing, documents, newsletters, projects, landing experiences, and attendee operations.

Platform administrators who work across organizations may use additional global event tools in the dashboard. This page focuses on organization events inside the customer management sidebar.

What Organization Events Cover​

Organization events cover programs, gatherings, conferences, workshops, hospitality experiences, member events, and internal or external activities that need operational follow-up.

An event record can bring together:

  • Organization ownership.
  • Created/responsible users.
  • Names and descriptions.
  • Languages.
  • Dates.
  • Place and address.
  • Tags.
  • Landing page link.
  • Event lobby and participant groups.
  • Invitations and participant states.
  • Registration limits and acceptance settings.
  • Name label settings.
  • Ticketing and payment-related configuration.
  • Newsletter link.
  • Project link.
  • Customer assignments.
  • Event documents.

CRM Connections​

Organization events connect to CRM through several relationships:

  • Assigned customers: contacts assigned to the event.
  • Event participants: attendee records that can link back to customers.
  • Projects: an event can be linked to a project for planning and delivery.
  • Newsletters: an event can connect to a newsletter audience.
  • Documents: event files stay near the event.
  • Mail templates and sent emails: communication and invitation flows can be investigated from event and email contexts.
  • Landing pages: events can link to guest-facing event experiences.

For attendance, invitations, ticketing, communication, or follow-up, support should inspect both sides: the event and the customer record.

Event Participants And Customers​

Event participants represent participation in a specific event/group. Customers represent the CRM contact record.

A participant can link to a customer. This link is important because:

  • Attendance and check-in history can become part of customer context.
  • The same customer can participate in multiple events.
  • Customer data can support name labels, communication, and follow-up.
  • Event operations can feed CRM tasks and protocols after the event.

If an attendee appears in an event but not in customer CRM context, check whether the participant is linked to a customer.

Event Projects​

Events can be linked to projects when the event belongs to a larger initiative with milestones, documents, tasks, protocols, participants, and mails.

Examples:

  • A multi-session conference project with separate event entries.
  • A sponsor activation project that includes several hospitality events.
  • A member onboarding project that includes private events and follow-up tasks.

Project linking is separate from customer assignment. A customer can be assigned to an event without the event being part of a project, and a project can contain events without every event participant being a project participant.

Newsletters And Event Communication​

Events can link to newsletters and mail workflows. This supports pre-event, onsite, and post-event communication while keeping CRM context intact.

Questions that usually resolve the communication trail:

  • Which newsletter is linked to the event?
  • Which customers are subscribed to the newsletter?
  • Which sent emails were generated?
  • Are participants in the correct event participant group?
  • Are invitation or registration settings limiting who can participate?

Ticketing And Admission Context​

Events can include ticketing, ticket types, payment status, participant groups, check-in, wallet passes, registration limits, and acceptance rules.

CRM support often needs to distinguish:

  • Customer record.
  • Event participant record.
  • Ticket purchase/order state.
  • Invitation state.
  • Check-in state.
  • Payment or refund state.

For detailed ticketing behavior, cross-check the product event docs and your finance or commercial documentation where relevant.

Permissions​

Organization event workflows stay scoped to the active organization and its event permissions. Event navigation appears when the user can list or read events, or when the user is a guide in the organization. Creating, editing, ticketing configuration, participant management, widgets, and mail template actions depend on event-related permissions and role setup.

If the events link is missing, check event list/read permissions and whether the user is a guide assigned to organization tours/events.

Common Support Scenarios​

A user cannot see organization events​

Check active organization, event permissions, guide status, and whether the user is in the correct organization workspace.

A customer is not visible on an event​

Check assigned customers, event participants, participant groups, and whether the participant is linked to the customer record.

An event is missing from a project​

Check the event's project link. Event assignment and project linking are separate.

An invitation or registration behaves unexpectedly​

Check accept-only-invited, registration limit, accept limit, request-acceptance-only, participant group requirements, and ticketing configuration.

Event communication is hard to trace​

Check event newsletter, sent emails, mail templates, customer subscriptions, participant groups, and the customer email tab.

Related concepts: Product: events, Widgets.