nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Warning message when creating Forms in a Space

Erick Orr

A user with Space admin and owner permissions created some forms and received this warning: Only users with “Work item create” permissions can submit this form. Your space is not currently set up to enable “Any logged in user”, which may prevent other users from submitting the form. If you wish to enable this, please contact your administrator. If I need to enable "Any logged in user", what are my specific steps to do so in Jira cloud?

Accepted answers

Arkadiusz Wroblewski

Hello @Erick Orr,

Does the warning block submissions, or appear only when configuring the form?

That exact warning was previously reported as a bug and marked fixed:
https://jira.atlassian.com/browse/JRACLOUD-96550

Before changing permissions, check Forms → select your form → Access.
- Open: Anyone with Jira access.
- Public: Anyone with the link, no Jira account needed. Public forms don't require Create work items permission.

Cheers,
Arek🤠🧙‍♂️

Sarah Marenchino | Devoteam

Hi Erick,

It is possible to allow logged-in users to submit a form, but I would first clarify the actual requirement before modifying the space permissions.

If your goal is simply to allow users to submit requests without accessing other work items in the space, I would recommend using a form with Public access, provided your organization's security policies allow it.

To configure this:

Open Forms in your Jira space.
Select the relevant form.
Click Access.
Select Public.
Configure the default Reporter required by Jira, then share the form link.

If the Public option is unavailable, a Jira or organization administrator should verify whether public form access is enabled in Jira's settings.

If you specifically want to allow all logged-in users to submit the form, you can select the Open option in the form's access settings.

If additional permissions are required in a company-managed space, you should review its permission scheme and the permissions granted to the relevant users.

However, I would highlight one important security consideration: the permission to create work items should not be confused with the permission to browse existing work items.

Granting Browse spaces to Any logged in user could expose all work items that are not otherwise restricted to the users concerned. Depending on the number of users with access to your site and the sensitivity of the information stored in the space, the consequences could be significant.

Work item security levels can restrict visibility, but I would not recommend relying solely on them to compensate for an overly permissive permission scheme. A configuration mistake or a work item created without the appropriate security level could be enough to expose sensitive information.

So my question would be: do you simply want more users to be able to submit the form, or do they also need to view and track the work items they create?

The answer will determine the most appropriate configuration without unnecessarily expanding access permissions.

All comments

Becker, Rene

What it means to say is, that if you want anonymous access to the form, use the lock icon and choose public. This will enable the form to be used without logging in (that's not a bad thing).

If you want to actually let people into Jira (/space), that do not have a login, you have to select Administration → System and enable Public Access. I would advise against it.

Ollie Guan

Hi Erick,

Existing answers cover basic permissions, but to fully resolve the warning, we need to clarify the project type and user identity.

Information Needed

Project Type: Is this JSM, Jira Software, or Jira Business?
Target Audience: Project members, all internal staff, or external anonymous users?

Supplemental Answer

JSM Portal Permissions: For JSM, check Project settings > Customer permissions first. Enabling "Anyone can send requests" is safer than modifying the core Permission Scheme.
License Requirement: Submitters must have Jira access. Without a product license, users will be blocked even if the Permission Scheme allows "Any logged in user."
Anonymous Limits: True anonymous submission is only supported via JSM public portals. Standard Jira forms cannot be accessed without login regardless of permission settings.

Arkadiusz Wroblewski

Hello @Erick Orr,

Does the warning block submissions, or appear only when configuring the form?

That exact warning was previously reported as a bug and marked fixed:
https://jira.atlassian.com/browse/JRACLOUD-96550

Cheers,
Arek🤠🧙‍♂️

Sarah Marenchino | Devoteam

Hi Erick,

It is possible to allow logged-in users to submit a form, but I would first clarify the actual requirement before modifying the space permissions.

To configure this:

Open Forms in your Jira space.
Select the relevant form.
Click Access.
Select Public.
Configure the default Reporter required by Jira, then share the form link.

If the Public option is unavailable, a Jira or organization administrator should verify whether public form access is enabled in Jira's settings.

If you specifically want to allow all logged-in users to submit the form, you can select the Open option in the form's access settings.

If additional permissions are required in a company-managed space, you should review its permission scheme and the permissions granted to the relevant users.

However, I would highlight one important security consideration: the permission to create work items should not be confused with the permission to browse existing work items.

So my question would be: do you simply want more users to be able to submit the form, or do they also need to view and track the work items they create?

The answer will determine the most appropriate configuration without unnecessarily expanding access permissions.

Erick Orr

This worked. Thank you!

Erick Orr

Making the form public did the trick. Thank you!

Arkadiusz Wroblewski

Nothing to thank for. We are here to help

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

space

forms

permissions