Skip to main content
Authentication & Players

Not translated yet — showing English.

Managing Players

Players is every account that has signed in to your game, in the environment selected in the top bar. Each player has one PlayServ player ID, whichever providers they sign in with. From here you can look a player up, see their sessions, devices and sign-in attempts, and suspend, ban or delete them. Open it from Players under Game in the sidebar.

The page has four tabs: Players, Roles (coming soon), SSO & Auth for the sign-in providers, and History.


The player list

Search by name, email or player ID, and narrow the list with the filters. Filters are kept in the page address, so a filtered view can be shared.

FilterValues
StatusActive, Suspended, Banned
ProviderThe sign-in provider a player has linked
Last seen24 hours, 7 days, 30 days, 90 days, or inactive for over 90 days or never
ColumnWhat it shows
PlayerName and email. A player who signed in without a provider shows a shortened player ID and anonymous player; one with a name but no email shows no email.
StatusThe account status, see below.
SSOThe providers linked to the account.
CountryThe player's country, when known. It's usually empty.
Last seen · JoinedLast activity, and when the account was created.
StatusMeaning
activeThe player can sign in and play.
suspendedSigned out and blocked from signing in. Progress and purchases are kept.
bannedSigned out, blocked from signing in, and the devices they used are banned too.
mergedThe account was merged into another one and no longer signs in.

Select players with the checkboxes to Suspend them, Export them as a CSV file, or Remove them permanently. Players whose owned data blocks deletion are skipped (see Delete a player); the confirmation still counts them as removed, so check the list afterwards. Export in the page header downloads every player as a CSV file: ID, name, email, status, providers, country, join date and last seen.


A player's details

Click a player to open their details. The header shows their name, email, player ID and status; the actions are at the bottom.

TabWhat it shows
OverviewIdentity: player ID, display name, email, country, joined, last seen and last IP. Then the accounts linked to the player, any identity collision, the reason for a suspension or ban, and devices and bans.
Auth attemptsEvery sign-in attempt, see below. A red count marks refused attempts.
Owned recordsEach data entity the player owns rows in, with how many rows and what happens to them if the player is deleted. Open an entity to page through its rows, or jump to it in Data.
SessionsThe player's signed-in devices.
ActivityThis player's lifecycle events: sign-ins, linked providers, suspensions, bans and the like.
PermissionsComing soon.

Sessions

Each session shows the device, whether it is online now, its location and IP, when it was last active and when it expires. Revoke signs that device out; Revoke all signs the player out everywhere. A revoked session's open connection is closed straight away, so a player in a match is disconnected. Revoking doesn't block the player: they can sign in again.

Devices and bans

PlayServ records a fingerprint of each device a player signs in from. It is only ever compared with the ban list, never used to recognise a returning player. The Device & ban enforcement card shows the player's fingerprint and their device-ban state.

ActionWhat it does
Lift…Removes the ban from one device. A reason is required. If the account is still banned, it stays banned.
Lift all device bans…The same, for every banned device of the player.
Rebind device…Records a new device for the player, given its 64-character fingerprint hash; the player ID doesn't change. The old device isn't signed out: revoke its sessions in Sessions if it shouldn't keep access. The dialog warns about a banned device or one that belongs to another player, but doesn't stop you. Use it to recover an anonymous player who changed devices.

Sign-in attempts

ResultMeaning
successThe player signed in.
failedThe credential was wrong, for example an invalid or expired provider token.
refusedThe credential was fine, but PlayServ declined: the device or account is banned, or the account is suspended.

Each attempt shows the provider (or Device for a sign-in without one), the reason, the IP, the device fingerprint and the time. Banners call out a run of refused attempts, with a shortcut to lift a device ban, and bursts of failed attempts from several IPs. Filter by result or provider.


Suspend, ban and restore

ActionAvailable whenWhat happens
SuspendActiveThe player is signed out at once and can't sign in. Progress and purchases are kept. A reason is optional.
RestoreSuspendedThe player can sign in again.
Ban…Active or suspendedThe player is signed out and can't sign in, and every device they used is banned, so they can't create a new account on it either. A reason is required.
UnbanBannedThe account can sign in again. A reason is optional.

The same actions are in each row's ⋯ menu in the list. Every action is recorded in History with who did it and why.

Open Ban

In the player's details, click Ban….

Give a reason

Enter why the player is banned. The reason is required and is shown on the player's details afterwards.

Confirm

Type the player's display name, or their player ID if they have no name, and click Ban permanently.

Unban doesn't unban the devices

Unban restores the account only. The devices banned with it stay banned until you lift them in Device & ban enforcement, so a player on a banned device still can't sign in.


Linked accounts and collisions

One player, several providers. A player can link Google, Apple, Epic and other providers to the same player ID, and sign in with any of them.

A player has at most one account per provider: a second Google account can't be linked to the same player until the first is unlinked. Unlink next to a linked account removes it from the player. A player must keep at least one: Unlink still shows on the last account, but unlinking it fails.

PlayServ never merges accounts on its own. When a provider account a player tries to link already signs in to another player, both accounts are left as they are and the player's Overview shows an identity collision. Review… lets you:

ChoiceWhat happens
Keep bothNothing changes; you can add a note.
Unlink from this playerThe provider account stays with the other player.
Unlink from the other playerThe provider account is freed for this one.

Merging two accounts is something only the player can do, from your game, by proving they control both: see User Login.

A merge moves sign-ins, not game data

When two accounts are merged, the linked providers move to the account that remains and the other one becomes merged. Progress, purchases and the data the merged account owns stay with it and are not copied. If the merged account was banned, the remaining one is banned too.


Delete a player

Delete player… erases the player for good, for example on a GDPR request: the account, its sessions and its linked providers. Before you confirm, the dialog shows what happens to the data the player owns, entity by entity, following each entity's on-delete setting:

Entity settingThe player's rows are
cascade-deleteDeleted.
anonymiseKept, without the link to the player.
restrictKept, and the deletion is blocked while any exist. Remove those rows first.

Confirm by typing the player's display name, or their player ID if they have no name.

Deleting a player can't be undone

There is no restore. If you only need the player gone for now, suspend them instead.

Export data at the bottom of the details downloads the player's summary as a CSV file. Their owned data is listed under Owned records.


History

History lists the newest 100 player-lifecycle events of the project, newest first: sign-ins, linked and unlinked providers, identity collisions and how they were resolved, suspensions, bans and their reversals, lifted device bans, merges and deleted players. Search them, or narrow them to a time range; both work on these 100 events.


Next steps

Last updated on 16 Oct 2026