New team-managed Jira space has no Access settings and creator cannot add tasks

Hi @Kimberle Lovitt 

Rovo recommendation is irrelevant here, as Jira Free lacks custom space roles and global settings do not display team-managed roles.

Issue is likely your Jira Service Management app access. Have an Org Admin confirm in Atlassian Administration that you hold an active JSM User/agent seat, as Jira Free is capped at 3 agents and creating a space doesn't automatically grant one. To test this, create a request via the space's Customer Portal versus the global Create button; success only on the portal indicates a missing agent license.

Best,

Arek 🤠

Hi @Kimberle Lovitt,

I think the missing Access menu and the "cannot create issues" error are the same problem, not two separate ones.

In a team-managed project, the Access section is only shown to someone who holds the Administrator role inside that project. If you do not hold that role, the menu is not empty — it is not rendered at all. That matches what you see: only Details, Automation and Apps.

Being listed as the owner or lead does not help here. The Lead field is descriptive and does not grant any permission by itself, so it is possible to be shown as the owner of a project where you hold no role.

One thing I would rule out: the Project roles page in Jira admin settings applies only to company-managed projects. Team-managed projects do not use those roles at all, so finding no associations there is expected and tells you nothing about this project.

"You cannot create issues in this project" then follows naturally — if you are in no role, you have no Create grant.

The way out is that another site admin or org admin opens the project and adds you: Project settings → Access, with the Administrator role. Org admins keep a route into a project even when nobody holds the project admin role, so this does not depend on the original creator.

For reference, team-managed business projects use Administrator / Member / Viewer, and the access level is Open, Limited or Private. A Viewer cannot create work items, so if you are added as Viewer the error will remain.

If the Access section still does not appear after you hold Administrator, then it is worth treating as a bug rather than a configuration issue.

One branch worth ruling out before you chase the role: which plan the Jira product itself sits on.

You can't edit space permissions or roles on the Free plan for software and business spaces, and a site can carry JSM Standard alongside Jira Free, so Space settings renders exactly as you describe for a reason that has nothing to do with your role. Worth checking that first, because on Free the Access page still won't appear once someone grants you Administrator.

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/