Org Command¶
The leadership side: who's in the org, where they sit, how they get promoted, and how the org pays for things.
Everything here lives under Org Management in the sidebar. Most of it is officer or admin territory — see Roles & Permissions for who sees what.
Member Homepage & Org Dashboard¶
Two landing surfaces, aimed at two different people.
Member Homepage is a member's own view — their upcoming events, awards and notifications, across every org they're in. It's always one click away in the sidebar, whatever module you're using.
Org Dashboard is the org's pulse: what's happening in this server right now.
Personnel Roster¶
Every member of the org in one list, with their rank, their billet and their history. It's the surface you actually use to run the org day to day — find someone, see what they fly, check whether they've been showing up.
Org Chart¶
Your org's structure, built as units containing billets — the posts people hold. Drag members into billets to assign them; units nest, so a wing can hold squadrons that hold flights.
Ranks are created and ordered here too. In Advanced permissions mode, ranks are also what the permission matrix hangs off, so the order you set here is the order your org actually runs on.
Ranks, promotions & awards¶
Promotion requests. Ranks can carry criteria — time in service, attendance, certifications — and members can request the next step when they meet them. Officers work an approve/deny queue, and an officer can also set a member's rank directly from the roster, which supersedes any request still open for that person.
Two switches control the flow: an org-level toggle for whether members may request promotions at all, and per-rank settings for whether a rank can be a promotion target or is hidden from the ladder entirely.
Promotions are a web workflow today
Approving a promotion updates the member's rank in Star Org Labs. It does not currently swap their Discord role or announce anything to a channel — that half is on the roadmap. Your Discord roles stay yours to manage (or to sync from your RSI org page).
Awards & certifications. Define your org's medals and qualifications, issue them to members, and let members pin them to their public profile. Certifications double as promotion criteria.
Recruitment Hub¶
A public apply page for your org and a review queue behind it. Applications land in the queue, officers work them, and accepted members flow into the roster.
The apply page hangs off your org's public website — see the CMS below.
Tickets & Support¶
Support that works from both sides of the wall.
Members open a ticket with /ticket create [category]. It becomes a Discord thread —
private or public depending on the category — and replies sync both ways. /ticket close
closes it when it's sorted. Only the ticket's author, the category's manager role, or an
officer can close one.
Staff work the same cases as a Kanban board under Tickets & Support: statuses, priorities, assignment, and internal notes that the requester never sees.
Categories are yours to define — Recruitment, Griefing Report, Ship Loan, whatever your org actually gets asked. Each can carry a manager role, an auto-assign role and an auto-close window:
| Command | What it does |
|---|---|
/ticket category list |
The categories members can pick from |
/ticket category add <name> |
Add one |
/ticket category edit <name> |
Rename it, or change its roles and auto-close days |
/ticket category remove <name> |
Delete it — once it has no tickets left |
A member-facing ticket page is rolling out
My Tickets lets members open and follow their own cases from the web instead of Discord. It's in early access; if you don't see it yet, your server doesn't have it turned on.
Org Treasury¶
A virtual bank in aUEC, with a ledger: deposits, withdrawals, taxes and payouts, each with who and why. Industrial sessions marked as org runs pay into it automatically when they close.
Goals¶
Org-wide objectives with material requirements — "we need 4,000 SCU of Quantanium for the next push." Members pledge what they've hauled and progress updates live.
| Command | What it does |
|---|---|
/goal pledge <goal_id> <item> <amount> |
Contribute toward a goal |
/goal create_template <template> <qty> |
Create a goal from a Wikelo preset (officer) |
/goal create_custom <name> <reward> <reqs> <qty> |
Build one from scratch (officer) |
Guild Points¶
Your org's own currency and standing. Points accrue through participation and are spent in the Loot Hub when a session runs on guild points — so the people who keep showing up are the people with the weight to win the next big drop. Officers manage the ledger here.
Alliance Hub¶
Orgs don't fly alone. An alliance is a bloc of orgs with an invite-and-accept handshake and its own roles. Once you're in one you get:
- Shared events — an op posted by one member org can be shared to the others, with a single roster instead of three
- A shared threat / KOS ledger — intel about hostile orgs and players, pooled across the bloc
Everyone in the org can read the ledgers; the controls that change them stay with staff.
Public Website CMS¶
Every org gets a public page — a slug, hero image, logo, a features list, social links and your theme — plus the apply page that feeds Recruitment. Admins edit it under Public Website CMS; no HTML involved.
Early access
The public page is switched off for every org for now — it is early access, not a paid feature (it used to need Champion-tier support; that is gone for good). The nav entry only appears once it is enabled for your server. To get in, ask in the community Discord.
It's a page, not a marketing site
The public page renders in the browser rather than being pre-rendered on the server, so search engines and link previews see less of it than a visitor does. Fine for "here's our org, here's how to apply" — don't count on it ranking.
Next: Roles & Permissions · Industrial