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.
A notification that also reaches you as a Discord DM carries one button, named for where it goes: View event, Open Loot Hub, View your ticket, Open Alliance Hub and so on (View in Star Org when there is no better name). It opens that page in Star Org. It never starts Star Comms; use a Launch Star Comms button for that (see Comms Ops).
Org Dashboard is the org's pulse: what's happening in this server right now.
Until the server's essentials are in place, admins also see a Finish setting up card at the top of the Org Dashboard. It lists what's left (the events channel, staff roles, and whether the bot can post), with Continue setup and Skip to full settings, and disappears once everything essential passes. See Getting Started.
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.
RSI org sync. In Server Settings → External → RSI Organization Sync, enter your org's SID (e.g. MONKEY), map each RSI rank name to Discord roles and turn on Auto-Role Sync. Verified members get the roles for their RSI rank automatically, every hour. A member the sync can't find in your RSI org twice in a row is marked "RSI: last seen in MONKEY" (your SID) on the roster; nothing is removed automatically.
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. On the Personnel Roster, each member's ⋯ Manage button at the end of their row holds Set Rank, Assign Billet, Issue Award and Grant Certification.
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.
The org-level toggle lives in Server Settings → Core → Access & Roles; when requests are off, the Promotions page says so and links straight there. When requests are on but no rank is marked Requestable on the Org Chart, the page points you to the Org Chart to fix it.
Promotions and Discord roles
If your org uses Discord role sync (Server Settings → Permissions; see Roles & Permissions) with a rank set to Rank → Discord or Both ways, approving a promotion also swaps the member's mapped Discord role. Otherwise the rank changes only in Star Org Labs. Nothing is announced to a channel; the member gets a notification.
Awards & certifications. Define your org's medals and qualifications, issue them to members, and let members pin them to their 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.
Anyone who can open the queue can approve and deny from it: officers and admins, and, if your server uses Advanced permissions, any rank you grant Recruitment Hub. Only officers and admins can choose which rank an approved applicant lands on. Anyone else approves them onto your org's default joining rank.
Nobody — officers and admins included — can approve or deny their own application, so the buttons don't appear on yours. Each application is decided once: if someone else got to it first, you'll be told and the queue refreshes to show the current status.
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, and anyone who could close it can /ticket reopen it.
Staff can /ticket claim a ticket (or assign it to someone else) and /ticket unclaim it.
Officers post an Open a ticket button panel with /ticket panel send and refresh it after
changing categories with /ticket panel update. A category can be set so that once a ticket is
claimed, only the claimer, the author or an officer can close it.
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¶
Open it under Treasury & Assets. 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.
Org Vault (on the aUEC & vault tab). Every org has a vault for items. Loot nobody claimed when a session ends is swept in, officers can add items by hand, and Send to Loot Hub puts an item back into an open session for members to roll on. The vault needs the Loot module.
Materials tab (rolling out with Industry v2). Lists the org's material payouts, deposits and withdrawals from the Org Stockpile, valued at UEX prices where known. A material payout — from an approved work order, or made by hand with New material payout (Industry Management) — is reserved in the stockpile until the member Confirms they collected it in game; an officer can Void one that hasn't been confirmed. It's a record, not a transfer: nothing changes in game by itself.
Role Menus¶
Self-assign role menus: members click a button (or react) to give themselves a role, such as
a game, a timezone or a ping you want. Build menus under Org Management → Role Menus and
post them to a channel. Officers can view menus; admins create and edit them. From Discord,
admins use /roles menu create, add, remove, post, update and delete, and
/roles menu list shows every menu.
Threat Intel¶
Early access: the Star Org Labs team switches it on per server.
Your server's own threat list for PvP. Look up an RSI handle to see who they are and whether your org has a verdict on them, keep dossiers, and give pilots or orgs a threat level. Every member can read it; adding and editing verdicts is for officers and ranks granted Threat Intel Management.
| Command | What it does |
|---|---|
/lookup <handle> [public] |
Who is this RSI handle, and is it on our threat list? Replies only to you; officers can set public to post it. |
/kos add · /kos remove |
Put a pilot or org on the list, change their level, or take them off (officers) |
/kos list |
The threat list, worst first |
/scoreboard |
How the list breaks down |
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