Start from the job, not the module name. Most events use more than one module, but each module has a clear centre of gravity.
Quick answers
- Use Core Event Workspace for the event record, dates, venue, status, modules, activity, and documents.
- Use Trader Manager for participant applications, approvals, compliance, participant payments, invoices, logistics, portals, and arrival check-in.
- Use Ticketing for public ticket sales, customer orders, attendees, ticket PDFs, refunds, and entry check-in.
- Use Stage Manager for performer applications, act profiles, stages, lineups, running orders, live show status, and running-order exports.
- Use Site Plan for venue layout, participant placement, infrastructure, zones, generated layouts, templates, and visual exports.
- Use Transport for vehicles, collections, deliveries, fixed departures, route optimisation, shared calendar feeds, Current RMS imports with selected PDFs, and driver job sheets.
- Use Document Centre when you need generated exports, PDFs, reports, invoices, or job sheets across modules.
How modules work together
- Start with the central event record so dates, venue, status, and documents stay aligned.
- Enable only the modules the event actually needs.
- Use module-specific setup for specialised work, then return to the event record when you need shared context.
If one event needs several workflows, activate several modules on the same central event record. That is the point of the shared workspace.
Related SmartGig pages
Relevant SmartGig pages
Related articles
FAQ: Why Can I Not See a Feature?
Work through package access, module activation, event setup, and role permissions when a page or button is missing.
FAQ: Billing, Payments, and Payouts
Separate SmartGig subscription billing from participant fees, ticket sales, invoices, Stripe Connect, refunds, and finance exports.
FAQ: How Do I Fix Wrong Applications, Participants, or Documents?
Correct the record without making the event history worse.
