Skip to main content

Player details

This page explains the player detail view for staff. It covers core admin actions and links to observability workflows without duplicating them.

Navigation path:

  • Server AdminPlayersOpen player

Access requirements

  • players.view to open player details
  • players.edit to change player data or delete a player
  • players.change_access_rights to edit user rights and groups
  • players.whitelist to whitelist/unwhitelist
  • players.change_money to access player transactions tab
  • players.see_position for routes visibility
  • logs.view + Log Explorer feature for embedded logs

Summary header

At the top of the page, you can quickly see:

  • current balance
  • verification state (linked account)
  • faction membership badges

Use these as a quick triage summary before deeper actions.

Settings tab

Use this tab to manage the player profile:

  • username and display name
  • notes for staff context
  • stored custom Wheel of Fortune wins
  • direct access rights (user-level rights)
  • group membership

Custom Wheel of Fortune wins appear in the same tab as a read-only history. Each entry shows when the player won it, the automation identifier, the stored text, and the wheel label that granted it.

For access rights strategy and default groups, see Access control.

Account status actions

The action buttons on the right of the header include:

  • whitelist / unwhitelist
  • unlink player — removes the linked user account from the player (see below)
  • delete player (if players.edit is granted)

These actions update Nitrado when Synchronize player lists is enabled in Settings.

To issue or manage bans and other restrictions for this player, use the Restrictions panel. You can filter the restriction list by player name to see all active and past restrictions for a specific account.

Unlinking a player

The Unlink Player action sets the player's linked user account to null. Use this when a player needs to re-link their character to a different account (e.g. they created a new Discord or platform account).

  • Requires players.edit
  • Only visible when the player currently has a linked account
  • A confirmation dialog is shown before the action is executed
  • The player can immediately link to a new account after unlinking

Transactions tab

If you have players.change_money, a Transactions tab appears. It allows admins to:

  • review player transaction history
  • add, remove, or set balances

For the money model, see Transactions concept.

Orders tab

The Orders tab shows the player's past shop orders.

If you have players.edit, the tab also includes Add free item to cart. Use it to place a free cart entry into the player's next checkout:

  • build the exact item list for the free cart entry
  • add raw items individually or copy all items from a shop item set into the list
  • set a custom cart title for the player-facing cart entry

When you use a shop item set here, the system copies the set's items into a free cart item. It does not link the cart row as a paid shop item set, so coupons and checkout pricing do not treat it as a normal purchased cart item.

Devices, sessions, routes, contacts, and logs

These tabs are part of the observability toolkit and are documented in Player observability:

  • Devices (linked accounts and device relationships)
  • Sessions (calendar timeline)
  • Routes (movement paths)
  • Contacts (proximity analysis)
  • Embedded logs (if Log Explorer is enabled)