Network owners

Discord members and server profiles

Find Discord members, inspect their server profiles and follow observed activity and departures across your network’s connected servers.

Browse all guides

This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.

Start here

  1. Open Workspace → Discord Members as the network owner.
  2. Choose a server or All accessible servers. Search by name, Discord ID, server or role; the table starts with 25 records per page.
  3. Active loads first for current members, including offline users. Left loads separately when you open it and shows members who have departed that server. Each tab keeps its own search and page.
  4. Select View profile to inspect available account fields, server profiles, roles, presence, activity totals and the latest observed events.

Connect and discover servers

An administrator installs the shared Discord bot, enables Server Members, Presence and Message Content intents in the Discord Developer Portal, maps the server to your network and restarts the deployed bot worker. Verified applications may need Discord approval for privileged intents. The initial member sync must finish before the member list is complete.

The owner sees only servers currently mapped to their network, even if bot commands are paused. Managers and sub-users cannot open the network-wide member directory. Administrators see all servers where the bot is installed, including unmapped servers.

Server sync status appears above the table. A disconnected bot retains its last observed records; disconnection does not mean every member left the server. A failed member sync never moves missing users to Left.

Membership and activity

Discord ID identifies the same person across servers. Each server membership keeps its own nickname, image, roles, join and leave times, status and activity totals. A person can be Active in one server and Left in another. Rejoining returns that membership to Active and preserves its history.

Messages, reactions, typing, voice-state changes and interactions update last observed activity across all channels the bot can access, including accessible threads. Command allowlists do not restrict member tracking. Online presence, custom status and activities are recorded separately; an online status does not prove activity in that server. All displayed times are UTC.

Last active in accessible servers includes only your own mapped servers. Profile event history is also limited to those servers. Only the selected tab loads and refreshes every 30 seconds while the page is visible. Switching tabs cancels an unfinished request for the previous tab; previously loaded tabs retain their search and pagination.

Available profile fields and history

The profile includes the bot-visible username, global display name, avatar, server nickname and image, roles and permissions, account creation and server join dates, boosting and screening state, timeout information, and other returned public fields. Available account banners, decorations and server tags are refreshed gradually through Discord’s API.

Discord’s bot API does not expose arbitrary members’ bios, private connections or private account fields. The profile explicitly labels bios unavailable. Invisible users appear offline. Activity before tracking began, activity while the bot was disconnected and activity in inaccessible channels cannot be reconstructed.

A leave event records when the bot observed the departure. If a complete member sync discovers a departure missed while the bot was offline, the event records the detection time and identifies the complete member sync as its source. The exact earlier departure time is unknown.

Member event history uses the bot’s activity retention setting, between 7 and 365 days. The profile shows the latest 100 retained events with metadata and profile changes. Membership records, totals and last activity persist when older events are pruned. Message text and private messages are not stored.

Frequently asked questions

Why are my servers missing?

Ask the administrator to confirm the bot is installed, the server is mapped to your network, the worker has been deployed and restarted, and the privileged intents are enabled. Check the server’s sync status.

Does Active mean online?

No. Active means the user is currently a member of that server. Their observed online presence is shown in View profile.

Why is someone listed more than once?

Each table row represents one person’s membership of one server. Use View profile to see that person’s memberships across the servers you can access.

Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.