Events overview
Understand how Events separates public discovery, attendee registration, invitations, Meet profile outreach, and organizer administration.
Events gives organizers one place to publish an event, review registrations, manage attendees and guests, and maintain the event’s agenda and communications. The public event page remains separate from its administrative controls.
The four Events surfaces
Event discovery
https://events.infra.one/{organization-slug} lists the organization’s Upcoming events and Past events. The list includes published events owned or co-hosted by that organization. A co-hosted event’s canonical direct URL uses the owning organization’s slug. Visitors can use Filters to narrow the list by date or country.
A published event appears in this list and is available by direct link. A hidden event is available only to someone who has its direct link. A draft is available only to an organization member or assigned event manager.
Event details and registration
https://events.infra.one/{organization-slug}/{event-slug} is the event’s customer-facing page. It can show the date, venue, description, hosts, speakers, agenda, gallery, attendee summary, and share controls according to the organizer’s settings.
Visitors can inspect a published or hidden event without signing in. Register requires an Infra One account. Registration is an approval workflow: submitting a registration creates a pending attendance rather than guaranteeing a place.
Invitations
Invite a friend is a separate authenticated invitation action, not the same thing as registration. The organizer can allow any signed-in user, Accepted attendees, Accepted attendees with a manual grant, or nobody. An invitation stores the introduction and attempts email delivery; the invitee still follows the event registration journey.
Event managers have a different invitation action for people who are already registered but have not completed a Meet profile. That email sends the attendee to Meet setup; it does not create another registration or invite-a-friend record.
Organizer administration
Manage events lists every event the signed-in user may manage. Organization members can manage their organization’s events. A person assigned as a direct manager can manage only the assigned events.
Each event has administrative areas for Details, Attendees, Guests, Board, Logs, and Email templates, plus actions for Gallery, Agenda, attendance report download, and duplication. The attendee browser includes a default Meet column that distinguishes completed profiles, missing or incomplete profiles, and the latest recorded Meet invitation.
The Meet workspace remains account-scoped: a person needs no organization role to set up a profile or use Meet discovery. The attendee-invitation action belongs to Events administration and therefore requires permission to manage that Event.
Event, registration, and invitation states are separate
An event has one publication state: Draft, Published, or Hidden. Each attendee has a separate registration state such as Pending, Under evaluation, Accepted, Rejected, or Cancelled. Each invitation also has its own record and later reflects the invitee’s registration state when the two become linked.
Changing one does not silently change the others. For example, publishing an event does not accept pending registrations, and accepting an attendee does not publish a draft event.
Registration targets are not capacity limits
The event form describes Signup target as “For internal measuring.” It does not stop new registrations when that number is reached. Organizers control attendance by reviewing registrations and changing their states.