ListGuard
A list several people can work on
Imported from the CRM export or the assistant’s spreadsheet, checked for duplicates and unreachable addresses, tagged by segment — VIP, press, partner, team.
Open the page →Corporate events
A corporate event is judged twice: at the door, and in the report afterwards.
Invitations under the company’s name, a team with the right roles, several doors, VIP and press lists, and a report for whoever asks how many people came — the guest side of a corporate event, run on one record.
Corporate Summit 2026Doors open
Checked in by segment
- VIP39 / 48
- Press17 / 20
- Partners112 / 140
- Team37 / 54
- Clients35 / 150
Doors
- Main entrance184 checked in
- VIP entrance39 checked in
- Press entrance17 checked in
Latest at the doors
- VIP guest checked in · VIP entrance
- Press guest admitted with approval
- Main entrance +6
- Partner arrival · Main entrance
Illustrative example — invented names and figures, not customer data.
Why corporate events are different
More people decide, more people watch, and somebody asks afterwards.
A launch, a client dinner, a dealer meeting, an internal day: corporate event guest management has demands a private party does not. The invitation goes out under the company’s name and has to look like it. Several people work on the list, and not all of them should see everything. There is a VIP entrance, a press list, a colleague at the door with no time to scroll — and afterwards somebody upstairs asks how many people came and expects a number that can be defended.
Winglark answers each of those with something that exists rather than a promise: a verified sender on your own domain, seven roles that match an event team, doors with named staff and a supervisor override that is recorded, and a report that names the people who promised and did not come.
More stakeholders
Marketing, an assistant, an agency, reception and management all touch one list.
Segmented guests
VIP, press, partners and the team are different promises with different doors.
Approval chains
Edge cases are decided by somebody with the right to decide, and recorded.
Brand consistency
The invitation goes out under the company’s name and has to look like it.
Multiple entrances
Main, VIP and press work at once, each with its own staff.
Accountability
Every admission names a door, a device, a person and a time.
Reporting expectations
The morning after, the numbers have to stand up to a question.
One event, many stakeholders
Many teams work on one event. They should not all see the same things.
The assistant needs the list, the agency needs its client, the receptionist needs a scanner and management needs the report. Giving everyone everything is the easy setting and the wrong one.
- Marketing
- Executive assistant
- Agency
- Reception
- Door staff
- Management
Same eventDifferent access
Role-based control
The corporate operations stack
One event at the centre, every part working on the same record.
The parts of Winglark a company event leans on most. Each links to its page. Choose a part to see what it does for a company event. Each links to its own page.
One corporate event
TemplateForge
Invitations that look like the company
Logo, programme, calendar button and reply button as blocks bound to the event; every published version kept.
Open the page →MailFlow
Sent under your own domain
A verified sender in your company’s name, and a delivery record per guest — delivered, bounced, suppressed.
Open the page →InvitePulse
Late additions, no duplicates
When the client sends twenty more names four days before, the new list is compared with the guests already invited, and only the genuinely new receive an invitation.
Open the page →Controlled access
Roles for the team
Owner, manager, marketing, guest manager, door staff, report viewer, partner staff. Door staff see the scanner and nothing else.
Open the page →GatePass
Several doors, named staff, recorded overrides
Main, VIP, press. A supervisor can admit an edge case, and the approval is recorded with a name and a reason.
Open the page →BadgeDesk
Name badges and a self check-in kiosk
Badges designed once and printed from the list — the whole list the night before, or each one as the door admits the guest — and a tablet kiosk at registration.
Open the page →Attendance evidence
A report that can be handed upstairs
Invited, replied, came — by name and by segment — exported as a formatted Excel or a presentable PDF.
Open the page →Guest segmentation
A segment should not disappear after the invitation is sent.
Tag a guest as VIP, press or partner once, and the tag stays on the guest record — in the replies, on the door screen and in the report. The segment stays operational for the whole life of the event.
412 guests
| Guest segmentation | Invited | Confirmed | Checked in | In the report |
|---|---|---|---|---|
| VIP | 48 | 44 | 42 | 88% |
| Press | 20 | 18 | 17 | 85% |
| Partners | 140 | 126 | 112 | 80% |
| Team | 54 | 52 | 50 | 93% |
| Clients | 150 | 98 | 59 | 39% |
Illustrative example — invented names and figures, not customer data.
Role-based access
Who sees what?
Seven roles, each read from the product’s own permission table. Choose one to see what it opens and what it does not.
Owner — Everything, including billing and deleting the organisation.
- Guest dataNames and contact detailsFull
- InvitationsCreate and sendFull
- DoorScan and approve exceptionsFull
- ReportsFullFull
- BillingFullFull
- Team and settingsFullFull
- Client scopeEvery clientFull
| Choose a role | Guest data | Invitations | Door | Reports | Billing | Team and settings | Client scope |
|---|---|---|---|---|---|---|---|
| Owner | Full: Names and contact details | Full: Create and send | Full: Scan and approve exceptions | Full: Full | Full: Full | Full: Full | Full: Every client |
| Manager | Full: Names and contact details | Full: Create and send | Full: Scan and approve exceptions | Full: Full | No access: No access | Full: Full | Full: Every client |
| Marketing | Limited: Names, contact details masked | Limited: Read only | No access: No access | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Guest list | Full: Names and contact details | Full: Create and send | Limited: Scan and admit | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Door staff | Limited: Names, contact details masked | No access: No access | Limited: Scan and admit | No access: No access | No access: No access | No access: No access | Limited: Assigned clients only |
| Reports only | No access: No access | No access: No access | No access: No access | Full: Full | No access: No access | No access: No access | Limited: Assigned clients only |
| Partner staff | No access: No access | No access: No access | Limited: Scan and admit | No access: No access | No access: No access | No access: No access | Limited: Granted per event |
Generated from the same permission table the server enforces, so this view cannot promise more than the product allows.
The event lifecycle
How it runs on Winglark.
Plan
Create the event as a corporate event
The type brings agenda, attendance mode and the questions a company event asks; segments tag VIP, press and partners.
Team
Give the team their roles
The assistant manages the list, the agency partner sees one client, the receptionist gets the scanner for the evening.
Invite
Send under the company’s name
A verified sender on your domain; the invitation designed from blocks the event owns, previewed as the real email.
Operate
Run the doors
Main, VIP and press on separate phones, each tied to a named person, all seeing the same list in real time — or offline, reconciled afterwards.
Report
Hand over the report
Invited, replied, came, by segment; exceptions listed with the approver; exported as Excel or PDF.
Several doors
Every door sees the same list. Every admission reaches the same record.
Main, VIP and press run on separate phones, each tied to a named person. A scan at one door shows at the others while the connection lasts, and a door that loses signal keeps admitting from its own copy of the list.
- Assigned staffOperators work the doors they are assigned to; a closed door admits nobody.
- The second scanAn already-used code is refused with the time and door of the first scan. A supervisor can approve a re-entry.
- No signalThe door keeps scanning against a copy with no contact details; the server re-checks everything when it reconnects and shows any conflict.
Event operations240
- Main entrance184Staff: Elif K.
- VIP entrance39Staff: Deniz A.
- Press entrance17Staff: Jonas W.
Illustrative example — invented names and figures, not customer data.
Exceptions and approvals
Exceptions should be recorded, not remembered.
Somebody important is not on the export; a code was already used; a guest arrives with one more person than they were allowed. A supervisor can decide — and the decision is written down with a name, a reason, the door and the time.
- Who approved it
- Why
- At which door, on which device
- When
Entry exception
- Guest
- Anna Müller
- Reason
- Name missing from the VIP export
- Door
- VIP
- Approved by
- Deniz A.
- Time
- 14:18
Approved
Illustrative example — invented names and figures, not customer data.
From promise to proof
RSVP tells you what people said. Attendance tells you what actually happened.
Because the reply and the check-in sit on the same guest record, the gap between them is measurable — by name and by segment.
- Invited
- 412
- Confirmed
- 338
- Attended
- 301
- Confirmed, did not come
- 58
- Came without replying
- 21
Attendance by segment
- VIP42 of 44 confirmed
- Press17 of 18 confirmed
- Partners112 of 126 confirmed
- Team50 of 52 confirmed
- Clients59 of 98 confirmed
Illustrative example — invented names and figures, not customer data.
Reporting
The second judgement: the report afterwards.
The exports a company is asked for, built from the same records the doors wrote — filtered by segment, door, reply or walk-in, and exported in the form a manager accepts.
- CSV · Excel · PDF — Filter by segment, VIP, door, reply, walk-in or offline admissions
- Exports that contain personal data ask for a reason, and the export is recorded.
Executive summary
- Guest list
- Invitation status
- RSVP details
- Attendance
- Door summary
- Door operations
- Devices and sessions
- Conflicts
- Executive summary
Before you choose an event operations platform
What to look for, for a company event.
The questions procurement and the event lead will both ask.
Is the invitation sent from the company’s own domain, with a sender that is verified rather than spoofed?
In WinglarkYes. Nothing sends from an address that has not been verified on your own domain.
Can the list be worked on by several people without everyone seeing billing and settings?
In WinglarkYes. Seven roles; billing belongs to the owner alone.
Can VIP, press and partner guests be tagged, reported on and routed to their own door?
In WinglarkTagged, replied and reported by segment, and shown on the door screen. Doors are separated by the staff assigned to them rather than by refusing other segments.
Does the door work on the team’s own phones, without signal, at several entrances at once?
In WinglarkYes. Any phone, several doors at once, and it keeps working without signal.
Is an exception at the door recorded — who approved it, and why?
In WinglarkYes. The approver, the reason, the door and the time are recorded.
Can the report be exported in a form a manager will accept, by name and by segment?
In WinglarkYes. CSV, Excel and PDF, filtered by segment, on every plan.
Where is guest data processed, who can export it, and what is not in place yet?
In WinglarkStated on the Trust & Security Center — including what is not in place yet.
Built for scrutiny
Corporate events are not only experienced — they are reviewed.
After the event come the questions: what it cost per guest who came, whether the VIPs turned up, why a name was let in at the door. Each answer should come from a record rather than from somebody’s memory of the evening. Winglark keeps that record as the event runs, so the review afterwards is a reading, not a reconstruction.
Agencies and client workspaces
Run several clients’ events without mixing guest data or context.
For agencies running events on behalf of clients, the same thing applies per client: a workspace each, data separated on the server, and partner staff who see only the client they are assigned to.
Every lookup is checked against the workspace and the client it belongs to, on the server. A record from another client behaves as if it does not exist.
Agency workspace
- Client A
- Client BTeam memberSees only the clients they are assigned to
- Client C
Corporate event types
What are you running?
Security and trust
What a company’s security team will ask, answered in public.
The Trust & Security Center describes each protection in detail. In short:
Explore Trust & Security- Each organisation’s data isolated; agencies can keep every client apart
- Role-based permissions enforced on the server
- Sign-in with Google, or a password stored with a strong one-way hash
- Guest data encrypted in transit and at rest, contact details masked by role
- Production kept apart from every test environment
- Every change tested before it is released
While the event runs
The keynote can hear the room.
Run the town hall’s Q&A through LivePulse, moderated before anything reaches the stage; put the venue, the times and every update on each attendee’s phone with Companion; and let the operations lead watch arrivals, doors and the room on Event Control Room.
Integrations
Connected to HR, CRM and the ticket site.
Replies and attendance go to your own systems as signed webhooks, the API adds guests from a registration site, and keys are scoped, expiring and revocable. The HubSpot sync and the Salesforce sync work today.
See the integrations →Questions
Can our company name and brand be on the invitation?
Yes. Invitations are sent under a verified sender on your own domain and designed from blocks with your logo. On the Agency plan the Winglark mark is removed from what guests see.
How do we keep VIP and press guests separate?
Tag them as segments on the list. Segments carry into the replies, the door screen and the report, and each door has its own assigned staff — the VIP entrance worked by somebody who knows the faces.
Who can see what?
Seven roles. Door staff see only the scanner; a guest manager sees the list and the invitations but not billing; a report viewer reads and exports only; partner staff see only their assigned client.
What if somebody important is not on the list?
A staff member with the right can add them at the door, and the record shows who did it. A doubtful case can be admitted with a supervisor’s approval, which is recorded with a name and a reason.
Where is guest data held, and can we get it out?
The security page states how data is protected and what is not in place yet. Every report exports to CSV, Excel or PDF at any time, on every plan.
Run the event with one operating layer.
Bring invitations, guest operations, access and reporting into one workflow.