> ## Documentation Index
> Fetch the complete documentation index at: https://learn.social.plus/llms.txt
> Use this file to discover all available pages before exploring further.
# Global Mute
> Stop a user from contributing content across the network while preserving their access to read — and learn how to apply a global mute in the Console
A global mute stops a user from contributing content across the network while preserving their access to sign in and read content they already have permission to see. They keep their account and memberships, but cannot create, edit or delete content while muted.
For spam or repeated disruptive posting, this gives moderators a temporary way to stop further contributions without cutting off the user's access to read. Removing an individual post addresses only that content; a global ban blocks the user's access to the network. A global mute sits between those actions and can be set to expire.
Global mute is applied by admins and moderators from the Admin Console. There is no self-service mute, and a muted user is never told who muted them.
## Mute, ban, and channel mute
| | Global mute | Global ban | Channel mute |
| ------------------------ | --------------------------------------------------- | ------------- | ------------------------------------ |
| Scope | Whole network | Whole network | One channel |
| Can sign in | Yes | No | Yes |
| Can read | Yes, content they already have permission to access | No | Yes, subject to existing permissions |
| Keeps memberships | Yes | — | Yes |
| Can post, comment, react | No | No | Yes, outside that channel |
| Expires on its own | Yes, if you set a duration | No | Yes, if you set a duration |
| Lifted by | A moderator, or the clock | A moderator | A moderator, or the clock |
Global mute and channel mute are independent. A user exempt from channel mute is still subject to a global mute, and lifting one does not lift the other.
## What a mute blocks
A mute blocks **content changes** — creating, editing and deleting content in the areas below. It does not remove the user's existing read access or prevent the listed non-content actions.
| Area | Blocked |
| -------------------- | -------------------------------------------------------- |
| Posts | Create, edit, delete |
| Stories | Create, delete |
| Scheduled posts | Create, edit, delete |
| Comments and replies | Create, edit, delete |
| Reactions | Add, remove |
| Polls | Create, edit, delete a poll |
| Messages | Send, edit, delete |
| Channels | Create (including starting a conversation), edit, delete |
| Communities | Create, edit, delete |
| Community categories | Create, edit, delete |
| Live rooms | Create, edit, end, delete |
| Events | Create, edit, delete |
| Area | Still works |
| ----------------- | ----------------------------------------------------------------- |
| Reading | Every feed, community, channel and profile they could read before |
| Membership | Joining and leaving communities and channels |
| Following | Following and unfollowing other users |
| Invitations | Sending and answering invitations |
| Polls | Voting in someone else's poll |
| Events | RSVPing to an event |
| Reporting | Reporting content and users |
| Blocking | Blocking and unblocking other users |
| Their own profile | Editing their display name, avatar and profile fields |
| Notifications | Their notification tray and notification settings |
Two of these deserve a moderator's attention:
* **Deleting is blocked too.** A muted user cannot delete their own past posts, comments or messages. If content needs to come down, a moderator removes it.
* **Reporting always works.** A mute never stops someone reporting abuse, and it never stops them leaving a community. Those are deliberately outside what a mute can reach.
Voting in a poll and RSVPing to an event stay open because they respond to something another member created — they are not the muted user publishing anything of their own.
## Muting a user
Go to Admin Console → **Users** → **Manage users**, and search for the account. You can also open the user's [Social History](/analytics-and-moderation/console/user-and-content-management/user-social-history) and act from there.
From the row's actions menu, choose **Mute globally**. On the Social History page the same action sits in the actions menu at the top of the profile.
Pick a duration under **Mute for** — 1 hour, 24 hours, 7 days, 30 days, or **Until I unmute them**. The default is 24 hours, and the dialog shows the exact end date as you change the selection.
Add a moderator note — "Why is this user being muted?". The note is kept with the record for your own audit and is never shown to the muted user.
Select **Mute user**. The Console confirms with "*\* has been muted".
The dialog states the scope as you apply it: *"A mute blocks new content — no posts, comments, reactions or messages. Reading, joining, following, voting and reporting still work."*
A mute takes effect immediately. The user's next attempt to write is refused, even if they are already signed in with the app open. Choose a duration according to your organization's moderation policy and the case at hand.
A timed mute lifts itself the moment it expires; nobody has to come back and clear it. An indefinite mute stays until a moderator removes it.
## Unmuting
Open the same actions menu and choose **Unmute globally**, then confirm with **Unmute**. The Console confirms with "*\* is no longer muted", and the user can post, comment, react and send messages again straight away.
You do not need to unmute before a timed mute expires. To change the length of a mute that is already in force, unmute the user and apply a new one — the Console offers **Unmute globally** for a muted account, not a second mute.
## Where a mute is visible
A muted account carries a mute icon in the users list, labelled **Muted** on hover. The row's actions menu shows **Unmute globally** in place of **Mute globally**.
A **Muted** badge appears with the user's other moderation badges at the top of the profile. Hovering it says either *Muted until \* or *Muted indefinitely*.
Every mute is recorded on the user's Moderation History timeline as **Globally muted**, alongside global bans, community bans and removals. Each entry shows who applied it, when, whether it was timed or indefinite, and the moderator note if one was left.
The timeline is the durable record — the badge only tells you about the mute in force right now.
**Unmuting is not recorded.** Lifting a mute removes the badge but adds no timeline entry, so the history shows every mute that was applied and not when any of them were lifted. If when a mute ended matters to your records, note it in the moderator note of whatever action you take next.
## What the muted user experiences
There is no mute notification or system message. The user can continue reading content they have access to, but an attempt to contribute content is refused. What they see when that happens depends on how the client app handles the refusal.
## Rules and limits
| Rule | Behaviour |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Brand accounts | Cannot be globally muted. The request is refused. |
| Community moderators | A community moderator is an ordinary member on the client side, so a mute silences them in the same way it silences anyone else. |
| Permission required | The same permission that governs global ban. See [Roles and Privileges](/analytics-and-moderation/console/moderation/roles-and-privileges). |
| Interaction with a ban | A muted user who is then globally banned cannot sign in at all; the mute is irrelevant until the ban is lifted. |
| Existing content | A mute is forward-looking. Content the user already published stays published — remove it separately if it breaches policy. |
## Troubleshooting
| Issue | Likely cause | Resolution |
| ----------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Mute option not available | Brand account, or your admin role lacks the moderation permission | Brand accounts cannot be muted; otherwise adjust role privileges |
| User appears to be posting after a mute | The user or timing of the action may need checking | Confirm the user ID and mute status in User Social History, then check when the post was created |
| Badge says muted but no end date on hover | The mute is indefinite | Unmute manually when the case is closed |
| Muted user still appears in a community | Expected — a mute does not remove memberships | Use a community ban or removal if they should leave the space |
| Muted user cannot delete their own post | Expected — deleting is a content change and is blocked | Delete it from the Console on their behalf |
## Next steps
Review the full picture before deciding how far to escalate
Control which admins can apply moderation actions
See where mute fits in the wider moderation workflow
Mute a single channel, or a user within one channel