An event hub for a single VATSIM vACC: pilots find events, controllers staff them, and staff plan them.
Hub: The whole vACC as this app sees it, spanning all of its FIRs. Avoid: Site, instance
Hub-wide: Applying across the whole Hub rather than in a single FIR. Every role can be held per FIR except Administrator, which is always hub-wide. Avoid: Global
Theme: The colors the whole Hub is shown in, chosen by an Administrator, either Default or VATSIM Scandinavia. Avoid: Skin, palette
Event: Something the vACC organises on the network, run by one FIR, taking place on one or more Occurrences. Avoid: Calendar entry
Draft: An Event not yet visible to pilots and controllers; only staff who can view or manage events see it. Avoid: Unpublished, hidden
Publish: To make a Draft Event visible to everyone and announce it on Discord. Rosters are also published, per Occurrence. Avoid: Release, go live
Occurrence: One date on which an Event takes place. Shown to people as a "date". Avoid: Instance, session
Slot link: An Event's link to an external system where pilots reserve arrival or departure slots. Avoid: Booking link, slot booking link
Shift Booking: A controller claiming a pre-defined shift on a position for an Occurrence. "Booking" on its own always means this. Avoid: Reservation, slot
Staffing Interest: A controller's statement that they want to work an Occurrence, with the positions they'd like. Avoid: Sign-up, application
Availability: The time windows within a Staffing Interest when the controller can work. Avoid: Interest window
Roster: Who works which position, and when, on an Occurrence: its shifts, booked or open, for an Event staffed through shifts, which are always public; or its Roster Entries for an Event staffed through Staffing Interest, once published. Avoid: Line-up, schedule
Roster Entry: A controller placed on a position for a span of time in an Occurrence's roster. Avoid: Roster slot, slot
Administrator: The built-in role that can do everything, always held hub-wide. Avoid: Admin, superuser
Event Staff: The built-in role that plans events and their staffing. Avoid: Event team, organiser
vACC Staff: The built-in role for vACC staff outside the events team, who can see every Event and its staffing but not change them. Avoid: Observer, read-only staff
Controller: The built-in role that may book shifts and show Staffing Interest; given automatically by the Controller source, or granted by hand. Avoid: ATC, rated member
Controller source: Whatever currently decides who automatically holds the Controller role, and where: either the hub's own rule (rated S1 or above in the vACC's subdivision, across the Hub) or one Integration feature. Only one is in charge at a time. Avoid: Roster provider, role sync
Pilot: What someone with no role is; not a role itself. Avoid: Guest, member
Sign-in provider: Where people sign in and get their VATSIM CID vouched for: VATSIM Connect, or VATSIM Scandinavia's Handover, which stands in for it. One per install, chosen when it's deployed. Handover the system has nothing to do with automatic roles being handed over to admins when a Controller source is switched off. Avoid: Auth provider, SSO, login method
Integration: A connection to one external system, such as the vACC's training system, that Administrators can switch on for the whole Hub. The Hub works fully with every Integration switched off. Avoid: Plugin, module, connector
Integration feature: One job an Integration can do, switched on separately, such as syncing the controller roster, syncing positions or pushing bookings. Avoid: Capability, sub-integration
Position catalogue: The Hub-wide list of known controller positions that staff pick from when adding positions to an Event. Avoid: Position list, position registry