Game Org module · Cross-game

Training in a gaming org isn't a Drive PDF and three DMs to an officer.

In most gaming orgs, training boils down to a pinned message in #announcements, a PDF on Google Drive that a member digs up when they remember it, an officer they DM to check if they've « really followed » the module, and a Google Sheet kept up to date one week out of two. Game Org replaces all of that with a catalog consulted inside the app, a built-in registration workflow, chained prerequisites to build real learning paths, and the learning material viewable directly inside the app. Binary for a simple course, full evaluation in Skills for a certification — you set the seriousness level course by course.

Deploy for free See the demo

A catalog inside the app, not a Drive link lost in a Discord channel.

A member who wants to train today usually has to scroll up a Discord channel to find the PDF shared two months ago, DM an officer to request registration, and pray for a reply before their next session. Game Org displays every course in your org inside a native catalog: operational section filters, cards with image and personal status, Courses / Certifications toggle. The member signs up in one click, fills in their availability if they want, it lands in the staff validation queue. And each course's learning material opens inside the app with one click on « Learn more » — no Drive link to find, no Google permission to debug. No external form, no extra tab.

  • Courses / Certifications toggle — counter badges on each tab, you see at a glance what's available and what's certifying
  • Section filters — clickable chips to isolate courses from a specific operational section, plus an « All » cross-section tab
  • Visual cards — course image (or section logo as fallback), short description, personal status (Requested, Approved, Rejected), prerequisites and trainers displayed
  • Built-in learning material — « Learn more » opens the attached document (PDF, Word, slides, image, video — any format) inside the app, zero Drive or Notion dependency
  • Built-in registration — « Sign me up » button, optional availability field, the request lands directly in the staff queue
Training catalog: Courses/Certifications toggle at the top with counter badges, section filter chips, grid of cards with image, colored status badge, Sign me up button on each card.
The member opens the app, they see what they can learn. No need to ask.

A course gets ticked. A certification opens a real evaluation.

Not every course is validated the same way. A safety briefing before an event is a yes/no — followed or not, that's it: the trainer clicks Train, done. A serious qualification — gunnery, advanced piloting, medical ops — deserves better than a checked box. In Game Org, a certification is tied to a skill: when the staff validates it, they don't slap on a quick score, they open the evaluation in the Skills module. The request moves to « under evaluation », and the certification is only truly earned once the skill grid is scored — tiers, groups, skills, one by one. Same catalog, same request queue; only the validation gesture changes: « Train » for a course, « Open the evaluation » for a certification.

  • Course = binary validation — approved or rejected, trainer comment. For anything « prerequisite to tick »: safety briefing, internal procedure, onboarding course
  • Certification = evaluation in Skills — validating it opens a full scoring grid (tiers · groups · skills) in the Skills module, not just a checkbox
  • Deferred earning — in the meantime the member stays « under evaluation »; the certification is acquired when the scoring reaches the required level
  • Same catalog, same queue — courses and certifications are requested in the same place and handled in the same queue; the staff clicks « Train » or « Open the evaluation » depending on the type
Requests tab of the Training Hub: a banner reminds that validating a course trains the member, whereas validating a certification opens their skills evaluation (the certification is earned afterwards). On the left, the sidebar of courses and certifications grouped by section with a pending-request counter. On the right, the « Marksman Qualification » certification selected with three member requests, each offering the « Open the evaluation » and « Reject » buttons along with the availability entered by the member.
A safety briefing gets ticked. A qual gets evaluated on a real skill grid.

A curriculum isn't a pile of courses thrown on a shelf.

An org that trains seriously builds paths — initial course first, specialization next, advanced at the end of the cycle. In Game Org, each course can be conditioned: prerequisite (another course already completed), minimum rank (you don't open the officer curriculum to a rookie), dedicated trainer role (to identify who runs the session). The org admin draws the tree as they see fit, creates their own labels, attaches their own materials. Not a catalog imposed by the vendor. The member sees on each card whether it's open to them or what's missing.

  • Prerequisite = prior course — to sign up for « Advanced combat », you must have completed « Combat basics ». The tool blocks registration until it's done
  • Minimum rank — a course can be gated from a certain hierarchy rank (lieutenant, officer, etc.)
  • Attached trainer role — each course can point to a Discord « trainer » role to identify who runs the session and receives requests
  • Free creation admin-side — name, description, image, material (any document), section, prerequisites, trainer role. Each org writes its own curriculum
Course edit screen admin-side: name, description, image, material (document, any format) fields, prerequisite dropdown listing the other courses in the org, minimum rank picker, trainer role picker.
Basics, then specialization, then advanced. A path, not a shelf.

Plan a training session as an event, registrations arrive on their own.

When you plan a training session as an event (type training), attendees of the event are automatically propagated to the trainer's Hub queue. No manual copy, no Excel export, no officer hand-writing the list ten minutes before the slot. The origin is preserved — the staff sees at a glance whether the request came from the catalog (a member who signed up spontaneously) or from an event (they registered for the planned session). One source of truth, two views tailored to the two jobs.

  • Training-type event — when planning, you tick the type, the event becomes a training session and triggers the bridge
  • Automatic propagation — each attendee lands in the trainer's Hub queue, with origin distinguished
  • Origin distinguished — SITE (spontaneous sign-up from the catalog) vs EVENT (via a planned session). The validator sees where the request came from
  • No double entry — the event carries the planning and the slot, the Hub carries the pedagogical validation. Both speak to the same database
Split view: on the left Events tab with a training-type event card and attendee list; on the right Requests tab of the Training Hub with the same members displayed, each tagged with a small violet « via event » label.
One planned session, attendees already in the Hub. No re-typing, no misses.

FAQ

Frequently asked questions

What's the concrete difference between a Course and a Certification?

A Course ends with a binary validation: the trainer says « followed » or « not followed », with a comment. No score. This is the right level for anything « prerequisite to tick » — briefings, internal procedures, onboarding course. A Certification, on the other hand, is tied to a skill: validating it doesn't grant the cert directly, it opens an evaluation in the Skills module. The member moves to « under evaluation », the trainer scores the skill grid (tiers, groups, skills), and the certification is earned when the scoring reaches the required level. This is the right level for serious qualifications — advanced combat, heavy-ship piloting, medical ops, section leadership. Same catalog, same request workflow, same Hub: only the validation gesture changes (« Train » for a course, « Open the evaluation » for a certification). You can perfectly well have 80 % binary courses and 20 % evaluated certifications in your catalog — it's a pedagogical choice that belongs to you, course by course.

How does a member sign up for a course, step by step?

Two possible paths, the member chooses. In the app: they open the training catalog from the menu, browse by section or in the global list, click on the card that interests them. A window opens with the full description, the learning material if there is one, the prerequisites displayed explicitly. They click Sign me up, fill in an availability field if the trainer needs it (optional), confirm. On Discord: they go to your server's #trainings channel and mention the relevant trainer role (e.g. @trainer-combat I want to sign up). The Game Org bot listens to the mention, links the Discord member to their identity in the app, creates the request in the Hub — without the member having to leave Discord. In both cases, the request lands in the same staff queue. As long as it's not handled, the catalog card shows a « Requested » status with a yellow pill. When the trainer approves, the pill turns green and the score appears if it's a certification; if they reject, it turns red with the trainer's comment visible on hover. No friction, no external form, no private DM to send.

How do you build a chained learning path with prerequisites?

The org admin creates the courses one by one with their name, description, image, learning material, minimum rank, trainer role. On each course, they can declare a prerequisite: a prior course to have completed. The tool enforces the rule — a member who hasn't validated the prerequisite sees the card greyed out with a « Course X required first » message. This lets you build a real pedagogical tree: onboarding course on arrival, then specialization by role (pilot, gunner, medic, logistician), then advanced at the end of the cycle. The admin can also reshape the tree over time without breaking everything — a course renamed or retired doesn't invalidate the history of completed validations, it simply stops being offered to newcomers.

What exactly happens when the staff approves or rejects a request?

In the training Hub, the officer sees the pending request queue, grouped by course (or filtered by member, section, rank). They click on a request, a window opens: they can Approve or Reject, and in both cases they can leave a comment. For a course, validating is enough — the member is trained. For a certification, validating doesn't grant it yet: the request moves to « under evaluation » and the tool offers to switch over to the Skills module to score the grid; the certification is earned once that scoring is done. At the confirmation click, several things happen at once: the member's card switches to the matching state in the catalog, their personal history is updated, a confirmation appears staff-side, and the org's statistics (members trained, per-course totals) recompute in real time. If the member had other requests pending, they stay in the queue — each decision is independent and handled in its own cycle.

How does the event sync actually work in practice?

When an officer plans an event in the Events module and ticks the training type, the event is flagged as a training session. Members who sign up for this event are automatically added to the request queue Hub-side, with a tag marking the EVENT origin (vs spontaneous catalog requests, tagged SITE). The trainer sees at a glance whether the request comes from an individual sign-up or an event planning. When validating, they can process the whole session group in a single operation (same score, same comment, bulk approval) or personalize the feedback member by member. Both modes coexist in the same Hub — the choice stays with the trainer.

Training and Skills module, is it the same thing or not?

No, these are two distinct modules that complement each other. The Training module covers the pedagogical curriculum finite in time — the member signs up, follows the curriculum, is approved or rejected by the trainer, with an optional score. The Skills module covers continuous, ongoing evaluation — mastery of a skill, scored continuously by the hierarchy, with automatic promotion when certain cumulative thresholds are met. And it's already wired: validating a training drops a badge on the member's profile, and validating a certification opens a skills grading grid to fill in in the Skills module. Pipeline: Training (the curriculum) → Certification (the curriculum evaluation, which opens the grid) → Skills (continuous evaluation). The two modules are connected, without substituting for each other.

And how does it look in practice?

See how Game Org takes shape inside your guild.

Cross-gameRecruitmentDiscord-first candidate pipeline, returnee detection, configurable integration path.Explore Cross-gameWelcome BotYour recruits onboard themselves on Discord — your flows, your questions, the right role assigned automatically.Explore Cross-gameHuman resourcesPromote, validate, decorate, benchmark — in a single tooled console.Explore Cross-gameSkillsMembers × skills matrix, fully custom hierarchy, automatic promotion, evaluation rights scoped by role and section.Explore Cross-gameEvents & calendarPlan once, publish to Discord, bidirectional signups — in a single tool.Explore Cross-gameMission ControlFrom the general order to each player's personal briefing — the op gets built once.Explore Cross-gameInsightsA command cockpit in six angles: engagement, members, operations, sections, decisions, events.Explore Cross-gameMiraYour Game Org copilot: a real face teaches you the app on video, an AI guides you day to day — and knows your whole org with Premium.Explore Cross-gameDiscord SyncYour members already live on Discord. So do your roles, your announcements, your signups.Explore Cross-gameSecurityGranular rights, per-org tenancy, no password to steal.Explore Add-on Star CitizenStar Citizen FleetDigitize hangars, aggregate collective power.Explore Add-on Star CitizenMission Control Star CitizenFrom the briefing to every gunner's brief — operations built seat by seat.Explore

Stop training your members with Drive PDFs and a hand-kept Sheet.

Create your Game Org space, build your catalog of courses and certifications, declare your prerequisites to build real learning paths, attach your materials — and let your members sign up themselves. Centralized validation staff-side, in-app viewer for the material, automatic sync with events. No intermediate demo, no sales form — the product is self-service from the moment you register your org.

Deploy for free