Dashboard
/dashboardReview organizer event summaries.
Synkron
BetaSynkron manages events from publication and registration through tickets, payments, QR check-in, attendee operations, and reporting. It supports in-person, virtual, and hybrid conferences, trainings, workshops, and public gatherings.
Beta operating manual
Synkron beta event manual
Create events, configure tickets and promotions, accept registrations, check in attendees, and reconcile payments and refunds.
Audience, scope, and prerequisites
Covers the current beta’s organizer and public event workflows, including ticketing, registrations, attendees, promo codes, check-in, and configured payments. Contracting, tax, accounting, venue safety, and external payment administration require separate procedures.
Who this is for
- Event organizers
- Registration and check-in staff
- Finance reviewers and Synkron administrators
Before you sign in
- An approved event owner, venue or online plan, dates, audience, capacity, privacy notice, and cancellation policy
- Approved ticket and payment configuration
- Authorized check-in staff and devices
- A refund and reconciliation owner
Roles and responsibilities
| Role | Access | Responsibilities |
|---|---|---|
| Organizer | Create events and manage tickets, promo codes, registrations, attendees, and event performance. |
|
| Check-in staff | Search attendees and validate QR tickets for assigned events. |
|
| Finance or administrator | Review payments, revenue, refunds, and tenant configuration when assigned. |
|
Create and publish an event
Public event information, capacity, tickets, privacy, and cancellation rules must be accurate before registration opens.
Create an event
Define event identity, timing, venue, capacity, visibility, and attendee information requirements.
- 1Search existing events
Avoid duplicate editions or test events on the public site.
- 2Enter core details
Set title, slug, description, organizer, date/time/time zone, location or online instructions, and visibility.
- 3Set operational policy
Record capacity, registration window, age/accessibility information, cancellation, privacy, and attendee communications.
- 4Save as non-public
Keep the event private or draft while tickets and public content are reviewed.
- 5Preview the public route
Test /e/{slug} on desktop and mobile and verify dates, links, terms, and contact information.
Expected result
A non-public event record has complete, reviewed operational and attendee-facing information.
Configure tickets and promo codes
Set capacity and commercial rules without allowing oversell or unintended discounts.
- 1Create ticket types
Set name, description, price/currency or free state, sales window, quantity, and per-order rules.
- 2Reconcile capacity
Ensure ticket allocations do not exceed venue or event capacity.
- 3Configure required fields
Collect only attendee information needed for delivery, safety, or legal requirements.
- 4Create bounded promo codes
Set exact discount, applicable tickets, usage limit, and validity period.
- 5Test calculations
Run free, paid, capacity, expired, and promo scenarios before publication.
Expected result
Ticket availability, pricing, capacity, required data, and promotions behave as approved.
Operate registration and attendance
Protect attendee data, prevent duplicate entry, and separate operational correction from financial adjustment.
Test and publish registration
Complete an end-to-end registration before sending the public link.
- 1Publish to a controlled audience
Make the event accessible for an internal test without announcing broadly.
- 2Complete registration
Test ticket selection, form validation, consent, promo code, payment or free completion, confirmation, and QR delivery.
- 3Verify organizer records
Confirm registration, attendee, ticket, payment, capacity, and communication state.
- 4Correct findings
Resolve content, form, inventory, payment, and email issues before launch.
- 5Publish the approved link
Announce only the final event slug and registration state.
Expected result
The attendee and organizer views agree for a complete test registration and the event is ready for its intended audience.
Check in an attendee
Validate one ticket once and handle exceptions without exposing the full attendee list.
- 1Confirm event and device
Open Check-in for the correct event and verify device time and connectivity.
- 2Scan the QR code
Use the live ticket; avoid photographing or copying the code.
- 3Verify result
Confirm attendee/ticket identity and valid, already-used, cancelled, refunded, or wrong-event state.
- 4Apply identity check
Use only the proportionate identity verification required by event policy.
- 5Resolve exceptions
Search by approved fields and route payment, duplicate, or transfer disputes to an authorized desk.
Expected result
A valid attendee is checked in once and exceptions remain traceable without bypassing ticket state.
Review a cancellation, refund, or reconciliation
Keep Synkron registration state and payment-provider state aligned.
- 1Verify request and policy
Confirm registrant, order, ticket, event, payment, cancellation terms, and approver.
- 2Review current states
Compare registration, attendee, check-in, payment, promo, and provider records.
- 3Execute the approved action once
Use the supported organizer or payment workflow and record its reference.
- 4Verify both systems
Confirm refund/cancellation amount, currency, ticket validity, capacity release, and communication.
- 5Reconcile reports
Account for provider fees, partial refunds, disputes, and timing differences.
Expected result
Registration, ticket, attendee, payment, and finance records reflect one approved action with a complete audit trail.
Security and data handling
- Collect only attendee data required for the event.
- Protect QR codes as bearer credentials until check-in.
- Separate event, ticket, payment, and refund permissions.
- Test capacity, pricing, promotions, and payment before publication.
- Use aggregate reporting and restrict exports containing attendee identity.
Known limitations
Read before relying on an unsupported workflow
These limits describe the source-pinned Synkron 1.0.0 beta scope and must be rechecked when the product changes.
- Synkron is beta and payment, email, refund, promo, and reporting behavior depends on tenant integrations.
- QR tickets can be copied; the first accepted check-in may consume validity.
- Public event information can be indexed or forwarded according to visibility.
- Offline check-in and later synchronization behavior was not verified in the current source.
- Provider settlement, fees, disputes, tax, and accounting remain outside Synkron’s event record.
Troubleshooting
You cannot sign in to Synkron
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
- Open the application from the approved portal and complete sign-in again.
- Confirm that the correct organizational identity and tenant are selected.
- If access is still denied, record the time and request an entitlement check from support.
A documented action or navigation item is not visible
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
- Confirm the role and prerequisites listed for the procedure.
- Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
- Ask the product owner whether the feature is enabled for the tenant before reporting a defect.
A saved change or background operation is not visible
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search for the item by its stable name or identifier.
- Do not repeat irreversible or externally visible actions until the original operation status is known.
A paid registration is incomplete or duplicated
Likely cause: Payment callback, browser retry, reservation expiry, or repeated submission produced inconsistent states.
- Do not create another charge or registration.
- Preserve registration/order and payment-provider references.
- Reconcile provider payment, Synkron registration, ticket, and attendee state before correction.
A valid attendee cannot check in
Likely cause: The ticket belongs to another event, is already used, cancelled/refunded, unsynchronized, or the QR cannot be read.
- Search by the approved attendee fields.
- Review ticket and payment state without exposing the full attendee list.
- Use a supervisor exception only under the documented event policy.
Contact support
Contact support when
- A repeatable Synkron error blocks an approved workflow
- Expected data, permissions, or tenant boundaries appear incorrect
- A security, privacy, compliance, or data-loss concern is suspected
- Payment and registration state disagree
- Capacity or pricing allowed an invalid purchase
- Attendee or event data appears across tenants
Include
- The page, action, and expected result
- The exact error text and time of occurrence, including time zone
- Your tenant, role, browser, and a sanitized record or item identifier
- Whether the problem can be reproduced and which troubleshooting steps were tried
Never include
- Passwords, access tokens, API keys, recovery codes, or session cookies
- Unredacted personal, health, financial, or other regulated data
- Private encryption keys or complete confidential documents unless an approved channel is provided
- Full payment card data, complete attendee exports, QR ticket images, or unnecessary identity documents