Server Management
Once you've set up a few subscriptions, these commands help you see what's configured, control notifications server-wide, and decide who's allowed to manage everything.
All commands on this page require the Manage Server permission by default, except /status, which anyone can run.
/status - View your subscriptions
/status gives you a read-only overview of every subscription in the server. It comes in two flavours.
Server overview
Run /status with no options to list all subscriptions.
Each row shows, at a glance:
- Whether it's active (✅) or disabled (❌)
- A ⚠️ marker if the subscription has a problem (see Issues below)
- A short summary in the form trigger → notify (e.g.
Anyone → Online only + 1 role)
The header line also tells you whether Global Subscriptions are on or off for the whole server - this reflects your /global setting.
Single-subscription detail
Run /status and pick a voice channel to see the full configuration for just that subscription:
- The exact trigger and notify rules
- The redirect channel (if any), cooldown, and per-join setting
- Whether notifications are enabled
If the channel you pick isn't a subscription yet, PingMan will point you to /setup-channel to create one.
Issues
PingMan never silently deletes a subscription when something it references disappears. Instead, it flags the problem so you can decide what to do. You'll see a ⚠️ in the overview and an Issues section in the detailed view when, for example:
- A triggering or notified user or role was deleted
- The redirect channel was deleted, or PingMan lost access to it
Open the subscription with /setup-channel and re-save it to clear the issue. See Editing a subscription.
/global - Pause or resume notifications for the whole server
/global is the master switch for every subscription in your server. It's handy for quieting things down during an event, or when you simply want a break from notifications without touching each subscription individually.
| Option | Effect |
|---|---|
enable: True |
All subscriptions resume firing notifications. |
enable: False |
All subscription notifications are paused server-wide. |
Info
Notifications are enabled by default. Pausing with /global enable:False doesn't change any individual subscription's own enabled/disabled state - when you flip it back on, everything returns exactly as it was.
The current global state is always shown at the top of /status.
/access - Control who can use which commands
By default, only members with Manage Server can run /setup-channel. With /access, you can grant that ability to specific roles without handing out the full Manage Server permission.
| Subcommand | What it does |
|---|---|
/access view |
Lists every command and the roles that currently have access to it. |
/access grant <command> <role> |
Gives the chosen role access to the command. |
/access revoke <command> <role> |
Removes that role's access. |
/access reset <command> |
Clears all custom access, returning the command to its default level. |
Info
Today, /setup-channel is the only command that can be delegated this way. Members with Manage Server always retain access regardless of these settings.
Warning
Managed roles - the automatic roles created by bot integrations - can't be granted or revoked access. Pick a normal role instead.
When a command has no custom roles assigned, /access view shows it as Default Access, meaning it falls back to requiring the Manage Server permission.
/quickstart - A short intro for admins setting things up
/quickstart posts a short, friendly guide right in the channel - what PingMan does, how trigger/notify sides work, and how to create your first subscription.
For the complete walkthrough, see the Getting Started guide instead.