A carrier has to send back a signed agreement. A customer's auditor needs the test report you hold. A contractor has 300 MB of drawings and no login.
The work item lives in Jira and the person with the file doesn't. The question keeps coming back: in 2018, in 2020, and again this February. Many of the older answers are out of date, because public forms launched without attachments and have accepted them since late 2025.
This article is for Jira admins. It maps the built-in ways to get a file from someone with no Jira account, or to send one to them, and where each way stops. On November 9, 2026 we ran a public form from start to finish on a Jira Cloud site and opened a JSM portal with no session. Everything else comes from Atlassian's documentation as it stood on November 19, 2026, linked at each option.
As of November 2026, someone with no Jira account can send files into Jira Cloud through a public form, the work item collector or, where the space accepts mail from outside, email. For files going the other way, the feature built for it is the secured attachment link in Jira Service Management customer notifications.
Files move in two directions.
Getting files into Jira
Public forms (software and business spaces)
On the space's Forms tab, create a form with an Attachment field, open Form access, choose Public and pick a default reporter. You need space admin permissions, and Jira asks you to confirm that anyone with the link will be able to respond. No app needed (Atlassian docs: Share your form).
We opened the link in a browser with no Atlassian session, typed an email address, attached two files and pressed Submit. Jira created a new work item with both files on it.
A public form as the outside person sees it, with no sign-in: the email address they typed, the form's fields and two files attached.
What we noted:
- Each response becomes a new work item, so a public form can't add files to one you already have.
- The sender isn't the reporter. Reporter and attachment author are the default reporter you chose. The address the person typed appears only in a comment Jira adds to the work item.
- The limit is 100 MB per attachment, according to the docs.
- The access dialog has two settings, the access level and the default reporter. There's no expiry date and no password, so the link works for anyone who has it until you switch the form off. Spam protection is reCAPTCHA.
Service spaces don't have this option: the suggestion to add public JSM forms, JSDCLOUD-17019, is still open.
The JSM portal and email (service spaces)
Portal customers don't use a Jira license, but they do end up with an account. With the option Customers can access and send requests from the portal without logging in, someone only types an email address to send a request: Atlassian's docs describe an account being created when they do, and a password to set before they can view it. Without that option they log in first. The portal we opened with no session showed "Enter your email to log in or sign up".
Email asks less of the sender. In a service space, someone without a license can create a request, comment and add attachments by email (Atlassian docs). Messages over 25 MB in total aren't picked up. If anyone can email the space, the sender becomes a customer automatically; if customers have to be added manually, mail from unregistered senders isn't processed.
The work item collector and public access (company-managed spaces)
The work item collector is a widget you embed on your own web page. Visitors need no account, and the form can include an attachment field. It exists only in company-managed spaces, and setting it up takes the Administer Jira global permission.
On Standard plans and above you can also grant Create work items and Create attachments to Public in a permission scheme. That opens the space to anyone on the web, so we left it out of our test on purpose.
Getting files out to someone outside Jira
Secured attachment links (JSM)
Under Space settings > Notifications > Customer notifications > Attachment security, you can let customers download attachments from notification emails without logging in (Atlassian docs). The links are for attachments on the comments customers get notified about. Each one expires 28 days after it's generated, and until then anyone who has it can use it; to end one sooner you delete the comment that holds the attachment. The setting needs JSM Standard or above.
Automation emails
The Send customized email action can carry attachments, but they're files you upload into the rule, up to 10 and 4 MB in total (Atlassian docs). Attaching the work item's own files is a suggestion with 98 votes, AUTO-1130, and a link to a work item's attachment needs a licensed Jira user to open it.
Guest access
For someone who'll work with you for a while, guests may be the better answer. On Standard plans and above they don't take a paid seat, and you can have up to 5 per paid user. A guest signs in with an Atlassian account and is limited to one software or business space, so this one doesn't suit the person who sends one file and disappears.
The scorecard so far
Option | Direction | The outside person needs | File limit | Where it stops |
|---|
Public form | In | The link, and an email address to type in | 100 MB per file | A new work item every time; no expiry or password |
JSM portal | In | A customer account, or an email address if anonymous access is on | Your site's limit, 1 GB per file by default | An account is created either way |
JSM email | In | A mailbox, if anyone can email the space | 25 MB per email | The size limit; the sender becomes a customer |
Work item collector | In | Your web page with the widget on it | Not documented | Company-managed spaces only |
Secured attachment link | Out | To be a customer on the request; the emailed link needs no login | Not documented | JSM only, Standard and above; a fixed 28 days; anyone with the link |
Automation email | Out | A mailbox | 10 files, 4 MB in total | Only files stored in the rule |
Guest access | Out, and in if permitted | An Atlassian account | Your site's attachment limit | Standard and above; one software or business space |
Where the built-in options stop
These options suit new requests and ongoing collaboration. The case the threads keep describing is narrower: the work item exists, one named person outside the company has to drop files on it or collect files from it, and the link should stop working afterwards.
We found no built-in link with an expiry you choose, a password or a download limit, and the suggestion to log attachment downloads in the audit log, JRACLOUD-75654, has 101 votes and is still open.
Full disclosure: we build Secure File Exchange at Terano Apps, and the steps below use it. Other file-sharing apps on the Marketplace cover parts of this too.
Step 1: Open the panel on the work item
Open View app actions > Secure File Exchange on the work item.
The panel on a work item, here after a file request has received two files.
Step 2: Create the link
Click Request files, choose when the link expires and which file types it accepts, add a password if you want one, and click Create link.
Expiry, file types and an optional password are set per link.
Step 3: Send it
Copy message gives you the link with a short note to paste into your email or chat. The app sends no email itself, and a password should go by another channel. The person opens the link in a browser, with nothing to sign up for or install. The page shows the work item's key and nothing else from it, and accepts up to 50 files of 1 GB each.
The upload page on a phone: the work item's key, the limits, and one file sent while another uploads.
Step 4: Pick up the files
When they finish, the app comments on the work item and mentions you. On a service space that comment is an internal note. Send files creates the same kind of link in the other direction, with an optional download limit; its card in the panel shows the downloads used.
One comment per upload, with a mention.
Two things to weigh first. Files received this way aren't Jira attachments: they stay in the panel for your retention period after the link ends, 30 days unless an admin changes it, so attach anything you need to keep. And files from outside aren't scanned for viruses, so treat them as you would an email attachment.
Check what's already open
- Public forms: under Settings > Jira apps > Jira configuration, Public forms sharing turns them off across the site, with separate settings for team-managed and company-managed spaces (Atlassian docs).
- Permission schemes: look for Public on Browse spaces, Create work items and Create attachments.
- What came in through public forms: the comment Jira adds makes those work items searchable.
comment ~ "\"response to a Jira form\"" AND created >= -30d
Where this lands in practice
- Anyone may send something, at any time: supplier applications or onboarding packs. A public form fits, as long as files stay under 100 MB.
- An ongoing customer relationship: the JSM portal and email, with secured links on the way back.
- One named person, one existing work item, one exchange: a link with its own expiry on that work item.
Quick answers
Can external users upload files to Jira without an account?
Yes. A public form takes attachments from anyone with the link, up to 100 MB per file. Each response creates a new work item.
Do public Jira forms support attachments?
Yes, since late 2025. Older answers saying they don't describe the launch version.
Can I make a Jira Service Management form public?
Not as of November 2026; the suggestion is JSDCLOUD-17019. Use the portal or the email channel instead.
How do I send a Jira attachment to someone with no account?
In JSM, turn on secured attachment links for customer notifications; the person has to be a customer on the request to get the email. In software and business spaces, the built-in route is guest access, which needs an Atlassian account.
→ Secure File Exchange - Share and Request Files for Jira
How do you get files from people outside your company today: forms, email or something else?
Michał Krysiuk, Terano Apps