Bans, Kicks & Warnings

How to issue and manage every type of moderation action — bans, kicks, warnings, tool bans, chat bans, and modcall bans — from the player profile page.

Finding a player#

All moderation actions start from a player profile. Go to Users in the sidebar and search by Roblox username or numeric user ID. The profile loads instantly from the Roblox API and shows all existing records alongside thumbnails.

Bans#

Issuing a ban

On the player profile, click the Ban button in the moderation action bar. Fill in the form:

• Reason — required. Shown to the player in-game when the ban enforcement kicks them.
• Duration — leave blank for a permanent ban, or enter a number of days for a temporary ban.
• Attachments — optional proof files (images, videos). Stored in the database.
• Classified — tick this to hide the reason and attachments from staff outside a linked investigation.

On confirmation the ban is created immediately and an audit entry is written. If enforcement is enabled in the SDK, the player is automatically kicked from any active server within seconds.

Temporary bans

Enter a number of days in the Duration field. The ban expires automatically after that many days. An expired ban is treated the same as no ban by the SDK.

Unbanning a player

On the player profile, existing bans appear in the Moderation tab. An active ban has an Unban button next to it. Clicking it sets the ban as lifted and writes an audit entry. The SDK will allow the player back in on next status check.

Kicks#

A kick removes a player from active servers without creating a persistent ban record. It is ephemeral — if the player rejoins immediately they are allowed in.

Click Kick on the player profile, enter a reason, and confirm. The kick is delivered to every server the player is currently in. An acknowledgement event is sent back by the SDK when the kick is received.

Warnings#

A warning creates a permanent record on the player's profile but does not remove them from the game. Warnings are counted and visible to all staff with user-view access. Use them to document minor infractions or as a first step before a ban.

Click Warn, enter a reason, optionally attach files, and confirm.

Punishments#

Punishments are targeted restrictions that go beyond a full ban. They appear under the Punishments sub-section on the profile.

Tool ban

Blocks the player from using their backpack (tools) in-game. The in-game SDK companion script (RoPermsClient.lua) hides the Backpack CoreGui when active. Can be temporary (days) or permanent.

Chat ban

Blocks the player from seeing or using the in-game chat. The client script hides the Chat CoreGui for both the legacy chat and TextChatService. Can be temporary or permanent.

Modcall ban

Prevents the player from submitting modcalls in-game. Useful for players who repeatedly abuse the modcall system. The SDK checks this status when a modcall.create request arrives.

Lifting a punishment

Active punishments have a Liftbutton on the profile. Lifting a punishment removes it immediately and writes an audit entry. The SDK will pick up the change on the player's next status check (typically within a few seconds due to cache).

Punishment attachments#

Images and other files can be attached to any moderation action as evidence. Files are stored directly in the database and served through the dashboard. Supported formats include images and video files up to the configured size limit. Attachments on classified punishments are hidden from staff outside the linked investigation.

Audit trail#

Every moderation action creates an audit log entry with the action, actor, target player, reason, and timestamp. You can review these in the Audit or Logbookpages. The player's profile shows a consolidated view of all actions taken against that specific player.