Understanding and managing user suspension




What's my plan?







All Suites

Team, Growth, Professional, Enterprise, or Enterprise Plus










Support

Team, Professional, or Enterprise







Verified AI summary ◀▼
Admins and authorized agents can suspend users who disrupt operations or spam. Suspended users can't sign in, create tickets, or receive notifications, and their requests go to the suspended queue. You can manage who can suspend users by adjusting role permissions. View and manage suspended users from the Customers page to maintain control over user interactions.




Admins and agents with permission can suspend end users who hassle agents or spam your
organization, post repetitive content, send unsolicited or abusive messages, or
otherwise take agents’ time and focus. Additionally, admins can suspend internal users
(agents) when needed.
This article describes what happens when an end user is suspended, how admins can grant
end-user suspension permission to agents, and how to identify suspended end users, and
how conversations are managed when an end user is suspended. See Suspending end users for information on suspending and
unsuspending end users.
This article includes the following sections:


About suspended end users
Managing who can suspend users
Viewing and managing the Suspended users list


Related articles:



Suspending end users


Suspending an agent’s account


About banning IP addresses from messaging
channels





About suspended end users

End-user suspension permissions are determined by the role assigned to an
agent. If an agent’s role allows them to edit end-user profiles, they can also suspend
messaging users. See Managing who can
suspend users for more information.
When you suspend an end user:

The Suspended tag is added to the user’s profile, their user essentials card, and next to
their entry in the Customers list.

The user can't sign in or create new tickets through any
channel, or through the API.

Users aren't notified that they have been suspended.

New support requests received from the user’s registered
identities are added to the suspended tickets queue.

The user no longer receives notifications from help center
articles or sections they follow.

If a ticket requester is suspended, they won't receive email
notifications for the ticket.

Suspended CC'd users don't receive notifications. Additionally,
any email replies they send are sent to the suspended tickets queue. If
a ticket has multiple CC'd users and at least one of them is suspended,
none of the CC'd users will receive notifications.

A ticket won't be created if a suspended user calls any of your
Zendesk phone lines.

Additionally, if the end user is suspended
from a messaging ticket:

The related messaging session
ends.

The conversation becomes inactive.

The messaging channel option in that ticket’s
composer is turned off. Agents can no longer add messages to the
conversation.

User messages in that ticket’s conversation are
no longer added to the ticket.

If your account is using multi-conversations, users can
continue to interact with any other ongoing conversations as if they have not
been suspended. This means that messages in these conversations from suspended
users will be viewable by agents, and added to the conversation’s ticket.

If a user has active tickets when they are suspended, suspending them will not
immediately block them from interacting with those tickets. They will no longer be
able to reply to existing tickets when one of the following events occur:

The ticket status is updated to
Pending, On-Hold, or Solved.

The ticket is Closed.

An agent ends the ticket’s related messaging
session.

The related messaging conversation becomes inactive.





Managing who can suspend users

End-user suspension permissions are determined by the role assigned to an agent. If
an agent’s role allows them to edit end-user profiles, they can also suspend
messaging users.


Note: By default, only the Admin system role can suspend end users. If you’re on a
Suite Enterprise plan, you can create a custom role to permit non-admins
permission to suspend end users.

To configure messaging user suspension permissions


In Admin Center, click
People in the sidebar, then select Team > Roles.
Select or create a custom role to configure for
end-user suspension.
Scroll to the People section on the role’s configuration page, then
under Manage end users, select one of the following:

View only, which allows agents to view the Suspended user list and
details for each suspended user, but does not let them suspend
users.

Add, edit, and assume profiles in organizations they belong
to, which allows agents to suspend end users who are part of
the same organization.

Add, edit, and assume profiles for any end users, which
allows agents to suspend any end user.

Add, edit, delete, and assume profiles for any end users,
which allows agents to suspend any end user.


Click Save at the bottom of the page.





Viewing and managing the Suspended users list

Suspension details are available from the Suspended users list on the Customers
page.
To view suspension details for a user

In Support, click Customers
( ) in the sidebar.
Click Suspended users from the Customer lists to show a list of
suspended users.
Find a user and select Edit from the options menu.
Details about the suspended user appear.



Additionally, you can search for suspended users on the Customers page using the is_suspended term.
For example:


is_suspended:true Otis returns all users named Otis who have been
suspended.

is_suspended:true returns all users who have been suspended.

If you've just suspended a user, it might take a few minutes for the suspended user
to be displayed in the list. Wait for a few minutes, then refresh your browser
page.



//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//

