Jira Form which is Open for Public Not accessible for Non-license users

[Vikrant Yadav]

Hi Experts,

Need your help in understanding Jira form access permission.

We have created a Jira form, which is open for Public. 

User who don't have account on Atlassian able to access the form but user which is having Confluence access but don't have Jira access getting error message you don't have Jira product access. 

If form is Public it should be accessible via Jira unlicensed user. 

[Staffan Redelius · Accepted solution]

Hi @Vikrant Yadav 

There are two places you need to set to allow public access to forms

For the form itself

1. Select Forms from the project navigation.

2. Select the form you’d like to edit.

3. Select Access ()

4. Select Limited, Open, or Public.

And under Jira configuration

1. Select Settings () from the top navigation bar in Jira.

2. Select Products.

3. Select Jira configuration from the side menu.

4. Use the toggle for Public forms sharing to turn the feature on or off.

Are both those settings set to public?

Let me know if this helps!

Best regards,
/Staffan

[Vikrant Yadav]

Thanks @Staffan Redelius  it's fixed. 

I was using the wrong sharable link. 

[Simon Hartshorn]

This resolved my issue too! I was linking directly from the form rather than creating a shareable link - that isn't actually specific anywhere that I could find

[Olha Yevdokymova_SaaSJet]

Hi @Vikrant Yadav 

That’s a really good observation — and it’s tied to how public form permissions currently work in Jira Cloud.

Even though a form is marked as Public, Atlassian distinguishes between:

1. Completely anonymous users (no Atlassian account), and

2. Users who are logged in but don’t have Jira product access (e.g., Confluence-only users).

✅ Anonymous users can access the form through the public link because Jira treats them as external visitors. There are field limitation avaliable for this form access type(attachments and some other fields are not avaliable)
❌ Logged-in Atlassian users without Jira licenses trigger the product-access check — so instead of being treated as “public visitors,” Jira blocks them with the “You don’t have Jira product access” message.

This is expected behavior and has been acknowledged in Atlassian’s documentation and issue tracker. The reason is that once an Atlassian account is recognized, Jira applies its product-level permission model — even for public forms.

If your use case involves collecting submissions from both logged-in Atlassian users and fully external users, you might want to consider Smart Jira Forms (developed by our team). It avoids this restriction entirely by allowing:

• True public access, regardless of whether the responder has Jira, Confluence, or no Atlassian product access.

• Secure one-time submission links or fully open forms.

• Attachments, custom confirmation messages, and automation mapping to create or update Jira work items seamlessly.

That’s a reliable workaround if you need universal form access — for example, collecting feedback, requests, or onboarding data from mixed internal and external audiences.

[Marc - Devoteam]

HI @Vikrant Yadav 

Forms are used in Requests that are on a JSM portal.

Any user with access to the JSM portal can use the form if they choose the request the form is used in.

Forms can only be accessed via the portal, not via Confluence.

Can you share more context, provide screenshots etc..