Admin Console

An in-game console for staff to look up players and phone data, moderate supported apps and fix account problems. Authorized staff open it with /ysadmin.

Before you start

• Deploy the full admin folder alongside the phone UI.
• Let automatic database setup finish first.

Grant access

Access is set in admin/config/server.lua, an editable file that only the server reads. Keep it server-only.

1. Grant the owner ACE (default yseries.owner) to your owner principal in your server config:

   Code

   Copy

   add_ace group.owner yseries.owner allow

   Use your real owner principal. This line does not add any player to that group.

2. As owner, open the console and create staff groups.

3. Give each group only the view and action permissions it needs.

Existing grants and revocations survive restarts and updates. Updating never resets or widens them.

Two settings to know:

• PermissionGroups.LegacyAceRoles maps legacy roles you list (by default admin) into group access.
• The Capabilities ACE labels are a migration reference, not grants. Adding every old capability ACE will not unlock an action.

What staff can do

View. The dashboard, player and number directories and app pages show supported records. Providers without support show an unavailable state instead of made-up data.

Act. Each action needs its own permission:

• content moderation and account restrictions
• password and PIN resets
• number management
• SIM suspension, reactivation and ejection
• Gallery recovery and deletion, where supported
• live map teleport and spectate

Cases. Staff cases collect linked subjects, notes and audit history. Creating a case does not moderate anything; use the app's own action for that.

Tools

• Notification playground sends test notifications, actions and live activities.
• Voice commands manages languages, phrases and custom actions. See Voice Commands, and keep its saved runtime file when updating.