NAVCOM AI Documentation

Documentation

Configure NAVCOM AI

Almost every server setting can be managed in two places: the web portal (recommended for bulk setup) and Discord slash commands (great for quick tweaks in-server). Both write the same database; choose whichever is convenient.

Portal: https://navcom.ai/login → Dashboard → Manage servers → select a guild.
Discord: type / and search for NAVCOM commands (admins only for configuration).

Getting started

1. Portal account

Web UI

  1. Open Register and create an account with email + password (min 8 characters).
  2. Check email for a verification link (also check spam). Use Resend verification on the login page if needed.
  3. Log in, open the dashboard, and click Link Discord.
  4. Optional: add your RSI handle under Add handle (bot-side /verify remains the trusted path for roles).

Password reset: Login → Forgot password → email link → set a new password.

2. Install the bot on your Discord server

Web UI

  1. Dashboard → Manage servers (requires Discord linked and Administrator on the guild).
  2. Find your server. If the bot is not installed, click Install bot and complete Discord’s OAuth prompt.
  3. When status shows Bot installed, click Manage settings.

You need the Administrator permission on the Discord server to manage it in the portal.

Verification

Members prove ownership of an RSI.com account. NAVCOM stores a global verification (works across NAVCOM servers) and can also store a local verification for one guild.

Member flow

Everyone

/verify [rsi_handle]

1) Run /verify YourHandle to receive a bio code.
2) Paste the code into your RSI profile bio and save.
3) Run /verify again (no handle) to complete.
Roles and nicknames update shortly after success.

Everyone

/remove_verification

Clears your global verification (and pending bio codes) so you can start over.

Everyone

/check_verification [user] [rsi_handle]

Inspect verification status for yourself, another user, or a handle.

Admin options

SettingWeb portalSlash command
RSI verified role — Discord role after successful verify Manage guild → Verification tab → RSI verified role /set_verification_role · /unset_verification_role
Verification checkmark — ✅ on nickname when enabled Verification tab → checkbox Part of nickname / server config (see nicknames)
Join verification DM — DM new joiners to verify Verification tab → checkbox /set_join_verification_dm (if available)
Local verify — guild-only verification without bio code — /local_verify @user handle · /remove_local_verification

Organization & rank roles

Map RSI organization short IDs (SID) and ranks to Discord roles. Rank numbers: 0 = lowest, 5 = highest (RSI rank ladder).

Web UI

  1. Manage guild → Organizations tab.
  2. Add org mapping: enter Org SID (e.g. WILDKNIGHT from the RSI org URL).
  3. Pick a Member Role for anyone in that org.
  4. Optionally set Rank 0–5 roles.
  5. Save changes (all tabs save together).

Slash commands

/set_org_role sid:WILDKNIGHT role:@OrgMember

/set_rank_role sid:WILDKNIGHT rank:5 role:@Leadership

/refresh_roles — re-apply roles for verified members in this server.

/view_server_config — review current settings.

Membership & rank scopes

When a player belongs to multiple orgs, these two settings control which orgs receive membership roles vs rank roles.

SettingMain organization onlyAll organizations
Membership roles — which orgs? Only the RSI main org gets a Member Role Every org membership can get a Member Role
Rank roles — which orgs? Only main org ranks 0–5 apply Ranks apply for every org they are in

Recommended presets

  • Main + Main — single-org focused server; ignore affiliate orgs.
  • All + Main — show many org memberships, but only rank-tag the main org.
  • All + All — full multi-org / multi-rank sync.

Web UI

Manage guild → Nicknames tab → Membership roles — which orgs? and Rank roles — which orgs?

Slash commands

/set_org_role_scope scope:Main organization only

/set_rank_role_scope scope:All organizations

Legacy preset: /set_multi_org_behavior (same three combos).

Nicknames

OptionMeaning
No changeNAVCOM does not edit nicknames
Org name[SID] Handle
Name orgHandle [SID]
Name onlyRSI name without org tag
Name sourceRSI handle (recommended) or display name
CheckmarkAppend ✅ when verification checkmark is enabled

Web UI

Manage guild → Nicknames tab.

Slash

/set_nickname_config — format and name source.

Welcome messages

Post a message when someone joins. Full Discord markdown is supported.

  • {user} — mentions the new member
  • #onboarding — auto-converts to a channel link if that channel name exists
  • <#1234567890> — raw channel ID mention
  • Backticks, bold, lists, links — allowed (max 2000 characters)

Web UI

  1. Manage guild → Welcome tab.
  2. Pick the welcome channel.
  3. Write the message (markdown OK). Save.
  4. Empty message disables welcome posts.

Slash

/set_welcome_message channel:#welcome message:…

/disable_welcome_message

Dynamic voice channels

Members join a starting voice channel; NAVCOM creates temporary channels (e.g. Squad 01) in a target category and deletes them when empty.

Web UI

  1. Manage guild → Voice channels.
  2. Add a row: starting channel, optional category, base name.
  3. Save.

Slash

/add_dynamic_vc starting_channel:… base_name:Squad target_category:…

/remove_dynamic_vc starting_channel:…

Action log

Optional staff channel where NAVCOM posts embeds for bot actions. Each event type is toggleable.

EventExamples
VerificationVerify success, local verify, removal
Role changesRoles NAVCOM adds/removes
Nickname changesNickname updates/resets
Welcome messagesWelcome post sent
Dynamic voiceCreate / join / delete temporary VCs
Member join / leaveOptional join/leave notices
Config changesPortal/slash configuration updates

Web UI

  1. Manage guild → Action log.
  2. Choose log channel (bot needs Send Messages).
  3. Toggle events. Save.

Slash

/actionlog channel #staff-logs

/actionlog events event:… enabled:True/False

/actionlog view · /actionlog disable

Bulk role refresh after a config save is summarized as one config event (not hundreds of role lines).

Star Citizen news

Post RSI Comm-Link / news feed items into designated channels.

Admin

/set_news_channel · /unset_news_channel · /test_news

Subscribe a channel, remove it, or post a test entry.

Lookups & help

Everyone

/citizen handle:… · /org sid:…

SENTRY-backed player and organization cards with links back to the SENTRY site.

Everyone

/help command_name:…

Short usage help for a specific command.

Common use cases

A. Org server with verified members + main-org ranks

  1. Install bot; set verified role (e.g. @Verified).
  2. Organizations: map your SID, member role, and ranks 0–5.
  3. Scopes: Membership = Main only, Rank = Main only.
  4. Nicknames: Name only or Name org; source = RSI handle; optional checkmark.
  5. Welcome: channel + message with `/verify` and #rules.
  6. Action log: staff channel, enable verification + role changes.
  7. Announce: “Run /verify YourHandle after adding the bio code.”

B. Multi-org alliance (many memberships, ranks only for primary)

  1. Map each allied org SID → membership role.
  2. Map ranks only for your primary org SID.
  3. Scopes: Membership = All, Rank = Main only.
  4. Save; run /refresh_roles if needed.

C. Event / pickup voice rooms

  1. Create a voice channel “Join for Squad” and a category “Active Squads”.
  2. Dynamic VC: starting = Join for Squad, category = Active Squads, base name = Squad.
  3. Players join the starter channel → temporary Squad 01, Squad 02… appear and clean up when empty.

D. Staff audit trail without spam

  1. Action log channel → enable Verification, Config changes; leave Member join/leave off.
  2. Disable Role changes if bulk refreshes are too noisy (config still logs a single summary).

Command reference (summary)

Everyone

/verify · /remove_verification · /check_verification · /citizen · /org · /help

Administrator (default)

/set_verification_role · /unset_verification_role · /set_org_role · /set_rank_role · /set_org_role_scope · /set_rank_role_scope · /set_multi_org_behavior · /set_nickname_config · /refresh_roles · /view_server_config · /local_verify · /remove_local_verification · /set_welcome_message · /disable_welcome_message · /add_dynamic_vc · /remove_dynamic_vc · /actionlog … · /set_news_channel · /unset_news_channel · /test_news

Some servers customize command access with role allow/deny lists (grant_command_access / related admin tools).

Permissions the bot needs

  • Manage Roles — assign verified / org / rank roles (bot role must sit above roles it assigns).
  • Manage Nicknames — nickname formats.
  • Send Messages · Embed Links — welcomes, logs, news, lookups.
  • Manage Channels · Move Members — dynamic voice (recommended).
  • View Channels · connect to voice as needed for VC features.

Portal users need Discord Administrator on the guild to manage it via the web UI.

Troubleshooting

SymptomWhat to try
Verify says code not found Confirm bio saved on RSI; wait a minute for SENTRY refresh; re-run /verify; ensure exact code.
Roles not applied Bot role hierarchy above target roles; Manage Roles permission; correct org SID; run /refresh_roles.
Nickname not changing Format not “No change”; Manage Nicknames; member not server owner (Discord restriction).
Portal can’t see servers Discord linked; you have Administrator; re-link Discord if token expired.
#channel not linking in welcome Exact channel name (usually lowercase-with-hyphens); or use raw <#id>.
Action log silent Channel set; event toggles on; bot can Send Messages in that channel.

More help: Portal · SENTRY · Privacy · Terms