Using the whitelist and blacklist to control access to Zendesk Support Follow

all plans

You can control access to your Zendesk based on your end-users' email addresses; either accepting or rejecting their attempts to register as a user in Zendesk Support or to submit support requests. You do this using the whitelist and blacklist. The whitelist can be used to allow access to everyone or just specific email addresses and domains. The blacklist, used with the whitelist, prevents access to all users who have not been added to the whitelist or specific users by email addresses and domains.

Email received from blacklisted users' domains and email addresses can be immediately routed into the suspended email queue or completely rejected, preventing tickets and accounts from being created.

The whitelist and blacklist are end-user settings.

In this example, the whitelist contains the MondoCam corporate domain. All email originating from this domain (including subdomains) are accepted. The blacklist is then used to declare that all other email is not users are blocked. This is done by adding an asterisk (*), which is a wildcard that blacklists (suspends) everything, meaning that all users will be blocked and prevented from creating and authenticating accounts. All email not received from the domain is sent to the suspended tickets queue.

You can however also reject users' email, meaning that it will not be added to the suspended tickets queue. There will be no record of the email in your Zendesk.

If you've configured Zendesk Support to accept requests from anyone, you can use the blacklist to filter out specific unwelcome users' email domains and addresses, such as spam.

Email that has been suspended as a result of having been blacklisted is added to the suspended ticket queue and flagged as blacklisted.
Note: To access your blacklist and whitelist, you must have Enabled selected next to the Anybody can submit tickets option under Admin () > Settings > Customers.

To edit your whitelist and blacklist settings

  1. Click the Admin icon () in the sidebar, then select Settings > Customers.
  2. Enter your whitelist and blacklist settings (see examples below).
  3. Click Save tab.
Note: If you place a wildcard (*) in the Blacklist, all users will no longer be able to create or authenticate accounts in any way, including via the interface, API, SSO, etc. You must add specific users to the whitelist.

Whitelist and blacklist usage examples

The whitelist and blacklist are used together to create rules for accepting, suspending, and rejecting users' email. Aside from the asterisk (*), which suspends all users', you can use the reject keyword to make the email bypass the suspended tickets queue and get deleted. However, note that reject only affects email and doesn't prevent users from creating an account in your Zendesk. The whitelist will automatically override the blacklist.

Approve a domain, suspend all others

This example whitelists one user's domain and suspends all others.

blacklist: *

You can also add more than one user's domain or email address to the whitelist. Separate each with a space.

blacklist: *

Approve a domain, but suspend specific email addresses within it

In this example, an entire domain is approved in the whitelist, all other users are suspended by using an asterisk in the blacklist, and then a specific email address within the approved domain aresuspended using the suspend keyword.
blacklist: *

Using this method, you can suspend specific email addresses from a domain that you have approved in the whitelist.

Approve a domain, but reject specific email addresses and domains within it

Similar to the previous example, a domain is approved in the whitelist and then exceptions to that approval are made in the blacklist. Instead of suspending a specific user's email address, it is instead rejected.
blacklist: *

This example also shows that you can add multiple email addresses and domains to the blacklist.

Approve all, but reject specific email addresses and domains

You can also leave the whitelist empty, meaning that all users are accepted, and then make exceptions for specific user's email addresses and domains.


Marking tickets as spam and suspending users

If email somehow makes it through the spam filter and your blacklist and tickets and new user accounts are created, you have two options for purging your Zendesk of both.

One of the ticket update options is Mark as spam and suspend user, which deletes the ticket and suspends the ticket requester. You can also select a user's account and suspend their access. For more information, see Suspending a user in the Zendesk Agent Guide.

A note about blacklisting people who have been CC'd on tickets

If you blacklist a user that has already been added to tickets as a CC, please note that blacklisting the user's email address will not remove themfrom those existing tickets. Also be aware that it is possible for agents to add blacklisted email addresses as CCs to new tickets.

Have more questions? Submit a request


  • 0


    I don't see the option to Mark as spam and suspend user in the ticket options. Was this feature taken off?  I only see Copy to forum, Create as macro, Merge into another ticket, and Delete.  Perhaps I am not the owner or I need special permission granted?

    Please advise and thanks!


  • 0

    Hi Norman,

    That feature has not made it into the new Zendesk yet (it's still in the Classic version though). It will be coming to new Zendesk soon, so don't worry! Sorry for the inconvenience!

  • 0

    Thank you for the quick response!

  • 0


    I need to stop the suspension of bounce backs for emails sent to clients with their invoices.  Can you filter them by subject heading? I can only see by email address currently.


  • 0

    Hi Alex,

    I believe you can try adding the following to your whitelist:

        subject:"some subject filter"



  • 0

    I have white listed all of my company email domains, but I'm still noticing that their tickets are getting held up in the suspended tickets section... Am I misunderstanding how this should work? I was thinking that if I white listed my company domains then they could complete the web form and they would not need to verified that they are the email owner... Also, I have recently started setting up some work flow approval and am running into the same issue. For example, I have a field associate that submits a ticket via the web form. I've designated that the ticket options they've chosen require approval from a senior operations leader without access to ZD. I've set that leader up as an email target and created a trigger that will place the ticket on "pending" status, email the ticket to the leader requesting work flow approval, and instructing them to reply with either "approved" or "declined" at which point my team would either process the ticket or push it back to the associate with the leaders response. Unfortunately what happens every time is the leaders reply to the ticket gets caught up in the suspended tickets section which has, at times, significantly impacted response times... any suggestions or help would be greatly appreciated.

  • 0

    Hello Colby,

    There are a few instances where the whitelist will suspend an email even if the domain or email is whitelisted. These situations usually involve potential security issues or mail loop situations. I believe the reason that your emails are being suspended in this situation is because you are sending out your notification as an email target. Zendesk does not authenticate targets to be able to respond, so when the email is sent back without an authentication token our system believes that it may be a spoofing attempt and suspends the ticket. If you need to have an end user put their input on a ticket I would recommend adding them as a CC to the ticket. If they are added as a CC, their email will contain the authentication token and allow the response to be added to the ticket. Using email targets is usually a great resource, but when you need the target to respond the CC functionality is much better suited.

  • 0

    We have "anybody can submit tickets" disabled, so I don't see the"whitelist" option.  When I check "anybody can submit tickets", I then see the "whitelist" option.  There is a domain listed there, but Zendesk is still determining (incorrectly) that some messages from that domain are spam and creating suspended tickets.

    Thus,I assume the whitelist filter is not in effect when "anybody can submit tickets" is disabled.  How do I leave that disabled and still whitelist a domain?


  • 0

    Hello Jim,

    The whitelist option is not given when "anybody can submit tickets" is disabled because it is up to the customer what end users to add in that use case (effectively whitelisting the users themselves). Anybody can submit tickets has to be enabled to see this option.

  • 0

    What are the mechanics of the blacklist when you have a rejected email, is it just ignored or is there any notice or response that goes back to that originating email?  We have triggered notifications that are going to customers via Amazon SES and some out of office and auto replies come back to our email address that comes into Zendesk and show up in suspended as coming from Amazon SES.  So if we blacklist the Amazon SES email address is it going to send any reject messages back to Amazon?  Or will this create an effective filter?  We want to receive actual responses to the notices which is why the reply email address comes to Zendesk but just trying to figure out filtering at least some of the known auto replies.  Thanks!

  • 0

    Hello Todd,

    When an address is added to the blacklist all incoming emails are directed to the suspended ticket queue. This is the red view that you can see at the bottom of your list of views. Triggers will not check their conditions against a ticket in the suspended ticket queue so no response email will be sent back to them. If you go in to the suspended tickets queue and recover these tickets, then the triggers will be checked against them and emails will be sent out.

    In the use case you described, I believe blacklisting the Amazon SES address would effectively prevent automatic responses from being sent back to Amazon. As long as you do not receive any incoming emails from this address that you need to respond to, only these out of office messages, there should be no issues that arise.

  • 0

    I have added  * to the blacklist but I am getting emails from outside our whitelist any ways

    it seems they are sending the email to and it creates tickets


  • 0

    Hey Jose,

    Do you think you could give me some ticket numbers or the email address that is making it through the blacklist? I'd love to take a look and see what's happening but I need to know where to start first.

  • 0

    ticket # 11660,11666,11667,11669,11671,11673

  • 0

    Hi Jose, 

    Sorry for the long delay, and thanks for the details. I looked at your suspended tickets queue and I see a few emails from addresses outside the domains you've whitelisted - this is the expected behavior when you use the '*' to blacklist all domains apart from those whitelisted. 

    It's possible someone recovered several suspended tickets by mistake; I looked up the ticket numbers you listed but they've already been deleted so I can't say for certain. 

    if you don't want these specific addresses to even create suspended tickets you'll want to add a "reject" condition to the blacklist - this will prevent suspended tickets from being made. You could have your blacklist look like this:

    blacklist: *

    For the "" address - I would not reject messages that come from that server - those messages should automatically be suspended anyway and you may actually want to look at them. Messages from that address can be helpful because they contain information about email addresses to which your messages could not be delivered, for example, when someone spells their email address incorrectly. In that case you might be able to correct the address and then send out a new message that you know will reach them. 

    Hope this helps, please let me know if you have more questions!

  • 0

    Thanks for the help on this I will try these solutions


  • 0

    Hi Guys,

    Is it possible to blacklist a domain that contains some string? For example, we are getting a lot of spam from users registering from

    Can I blacklist a domain like this:



  • 0

    Hi Ray, 

    I see you have a ticket with us - we'll update you through there very soon. I'm sorry to report there isn't a way to blacklist domains that way with various strings at the front. I think we have some other options for you on this though, we'll be in touch soon through the ticket! 


  • 0

    can i use in blacklist * reject:* ?

    I have no way of noing specific email addresses spam going to cam from. And I really want to reject everything outside of my whitelist.

  • 0

    Thanks for the article; this is exactly the info I needed. Very helpful

  • 0

    Hi Andrey,

    Perhaps a better way to accomplish the same goal would be to turn off "Anybody Can Submit Tickets" in Settings>>Customers. Then, the  only people who could submit tickets are those people that you already have in your Zendesk User profiles, you wouldn't have to add all of them to your whitelist. Would that work?

  • 0

    Hi Support,

    I have a request that may concern blacklists - I'm sure you can help me clear it up.

    My ZD currently receives wall posts from FB - which we like ;)

    However, when I post company info on FB (as company) these appear in ZD as tickets and are clogging up the joint.

    What is the best solution you would recommend?

    Thank you!


    PS. FB end-users don't have emails listed so I'm not sure how to blacklist it if that's the advice, also I'm leery of blacklisting any email that has the company domain in it (sounds like a recipe for bad pudding ;)

  • 0

    you can create an automation and have the unwanted post put to a group and have them deleted

  • 0

    there a facebook email associated to.the.account

    here article on it sovif you want to use it for blacklisting thqt might be an option

  • 0

    Hi Marshall, 

    I would not recommend blacklisting the email address, I think that could get very confusing and I'm not sure it would work well. 

    One option you do have is to turn off the "include post made by author" setting (Admin > Channels > Facebook > edit). This means if you make a post on the page as the auther, Zendesk will ignore it and not make a ticket out of it:


    One note about turning that setting off, if an end-user comments on a post you make as the author of the page, it too will not be made into a ticket. 

    If that isn't something you want to do I would suggest finding a workflow similar to what Jose mentioned - maybe tagging these tickets and then have a trigger that automatically closes these types of tickets. Hope this helps, let me know if you have more questions!

  • 0

    can i use in blacklist * reject:* ?

    I have no way of noing specific email addresses spam going to cam from. And I really want to reject everything outside of my whitelist.

  • 0

    Thanks Jose and Laura!

    I think this will do the trick for now.

    "[not] Include Wall posts authored by the Page"


  • 0

    @Andrey You can add t an asterisk (*) to blacklist everything except the domains added to the whitelist (Without the Reject) 

  • 0

    @ Trisha Patel, is the sintacks looks good?


    or I need a space like:

    t *



  • 0

    t* would be correct

    t * would look for t with a space

Powered by Zendesk