Enabling attachments in tickets

Agents and end users can send each other attachments through tickets. For more information about how to send an attachment as an agent, see Adding attachments to ticket comments. Zendesk Support accepts attachments from users sent in via the API, email, web form, and Web Widget channels in your Help Center. Users cannot send attachments through social media channels.

Administrators can configure how attachments are handled in a number of ways, including setting privacy rules, end user permissions, and attachment methods.

Note that attachments are not indexed by search engines unless the link for the attachment itself has been published in a Help Center article or something similar. This is the case whether Require authentication to download is on or off.

This article includes the following topics:

• About email attachments
• Enabling email attachments for agents
• Allowing end users to attach files to tickets
• Enabling private attachments
• Attachment size limitations
• Scanning attachments for viruses

About email attachments

Agents and end users can add attachments when creating or updating a ticket, or replying to an email notification. The attachments become linked attachments, which are links to external files that can be used to download the attachments, if and when they’re needed. This is the default behavior for attachments sent by email and this is what happens when email attachments are not enabled.

If email attachments are enabled, the behavior is different. Agents and end users can send email attachments instead of linked attachments. Email notifications caused by creating or updating a ticket, or replying to an email, include actual attachments, instead of links to attachments. Email attachments appear as images and are a preview of the first page of the file.

It's also important to note that there are two types of email attachments:

• Inline attachment: You can drag and drop files into the body of an email or comment. The image of the file appears wherever you dropped the file.
• Appended attachment: Attachments that appear at the bottom of a comment and that send as part of the comment's email notification.

Email attachments are enabled by the administrator using the Include attachments in emails option. This option is disabled by default.

When email attachment file size limitations are exceeded, links to attachments appears in email notifications instead (see Attachment size limitations).

Enabling email attachments for agents

The default attachment configuration allows your agents to add files to ticket comments and email notifications as links. You can allow agents to attach files directly to the comment. This type of attachment is stored in Zendesk Support and is accessible from the ticket interface. You can attach any file type you want.

You an also allow end users to add attachments to tickets (see Allowing end users to attach files to tickets).

To enable email attachments

1. Click the Admin icon () in the sidebar, then select Settings > Tickets.
2. Under the Settings tab, select Include attachments in emails.
   Note: This setting does not appear and cannot be enabled if Require authentication to download is enabled.
3. At the bottom of the page, click Save tab.

Once enabled, when an agent attaches a file to a comment, it is included as an attachment rather than a link.

Note: Only files attached to the current ticket comment are included in the email notification. Files attached to earlier ticket comments are not attached to later email notifications.

Linked attachment example	Email attachment example

Allowing end users to attach files to tickets

You can allow end users to send attachments when filing a ticket or responding to an email notification. The permissions granted to agents, described in Enabling email attachments for agents, apply to end users when this setting is configured.

To enable attachments from end users

1. Click the Admin icon () in the sidebar, then select Settings > Tickets.
2. Next to Attachments, select the Customer can attach files check box.
3. Click Save tab.

Enabling private attachments

If you have Guide activated, you can make attachments private so that users need to be logged in to view shared file links in tickets or email notifications. If you don't make attachments private, the shared file link can be viewed by anyone.

Important: If you enable private attachments, it will also disable inline images for users who are not signed in.

If sensitive documents are attached to your tickets, especially identification documents such as passports and driver's licenses that can be used for identity theft, we recommend that you enable private attachments. Private attachments are enabled by turning on the Require authentication to download option (off by default). If you decide to leave this option off and an email notification is misdirected to someone other than an end user, sensitive information may be accidentally exposed to non-users. For example, the non-user might decide to click the shared file link in the email and then the attachment displays.

Note the following about using Require authentication to download:

• Private attachments can only be used if Guide is activated. If Guide isn't activated, Require authentication to download prevents end users from downloading attachments since they cannot be authenticated.

• Unless Require authentication to download is associated with a specific group or agent, attachments are visible to any authenticated user. Once an attachment is associated with a ticket or post, visibility is restricted to users with access to the ticket or post that has the authentication to download.

• Attachments are not indexed by search engines unless the link for the attachment itself has been published in a Help Center article or something similar. This is the case whether Require authentication to download is enabled or not.

To enable private attachments

1. Click the Admin icon () in the sidebar, then select Settings > Tickets.
2. Next to Attachments, select the Require authentication to download check box.
   Note: Include attachments in emails does not appear and cannot be enabled if Require authentication to download is enabled. Additionally, when you enable Require authentication to download, agents will not be able to copy and paste images from their computer into ticket comments.
3. Click Save tab.

Attachments are not indexed by search engines unless the link for the attachment itself has been published in a Help Center article or something similar. This is the case whether Require authentication to download is on or off. Additionally, when this setting is enabled users will not be able to copy and paste images directly in to tickets.

Attachment size limitations

There are file size limitations for attachments. Make sure that you understand how these limits affect whether an attachment can be delivered as an email attachment, or must be delivered as a linked attachment instead.

The limits described in this section are about email attachments only and don’t apply to linked attachments. If your plan includes a higher ticket file attachment size (for example, Professional or Enterprise), don’t worry—you can still send links to attachments that exceed the limits mentioned here, up to the limit specific by your plan.

Here are the file size limitations for attachments:

• Support Essential: 1 MB
• Support Team: 7 MB
• Support Professional and Enterprise: 20 MB

If you exceed these limits, the attachments are sent as linked attachments instead. Attachments from earlier comments are included in email notifications as linked attachments as well.

If you add multiple attachments in a ticket response, they are prioritized based on the attachment type and size. Inline attachments take precedence over appended attachments when calculating these limits. Note that when inline attachments are sent as links, they still appear as images in the body of the email notification. The scenarios below describe how this works.

Scenario 1

Two files are attached in the following order:

• Email attachment A (3 MB)
• Email attachment B (6 MB)

Behavior:

• Files A and B are included as email attachments.

Scenario 2

Three files are attached in the following order:

• Inline attachment A (5 MB)
• Email attachment B (5 MB)
• Email attachment C (4 MB)

Behavior:

• Inline attachment A is sent as an email attachment.
• Attachments B and C are included as file links, as they push the total email attachment file size over 10 MB.

Scenario 3

Three files are attached in the following order:

• Inline attachment A (5 MB)
• Inline attachment B (6 MB)
• Inline attachment C (4 MB)

Behavior:

• Attachment A is included as an email attachment.
• Attachment B is included as a file link, as it pushes the total email attachment file size over 10 MB.
• Attachment C is included as a real attachment, as it brings the total email attachment file size to 9 MB.

Scanning attachments for viruses

All files attached via email are scanned for harmful viruses before being sent in an email notification. If an attachment is found to include a virus, it is not included in the email notification. Instead, the recipient is sent an error message stating an attached file was not sent, and recommends they contact the original sender.

The sender does not receive a notification when an attachment is not sent.