Granting project type access to users

[Jaclyn Klaus]

Hi all, 

I'm pretty new to Jira and am having trouble understanding how to grant certain permission types to users in my organization. I need all members of my organization to have access to creating new Kanban boards. Currently, most only have access to create new Agility boards, even with elevated privileges. Is there a place in settings where I can allow them to have access to create multiple types of boards? Or is this just permission that is given with administrator standing?

I have seen the documentation regarding creating boards in general, which has the solution as "Jira Global Permissions > Create Shared Objects". I'm not so sure this is the solution to the issue here, though.

Thank you!

[Joe Pitt · Accepted solution]

Only administrators can create projects. If every user needs to create projects you'll need to make EVERYONE administrators which will ultimately lead to problems with people doing what they shouldn't.  JIRA doesn't have field level security. 

[Joe Pitt · Accepted solution]

I don't know about the Kanban question, but being new there is a common problem with permissions you should know. 

JIRA works by GRANTING access. You can't restrict access. By default, JIRA grants access to the group used to logon (used to be JIRA-users but may be different on your version).  

1. The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.
2. Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
3. One permission scheme will cover almost all projects. The project admin controls project role membership

[Jaclyn Klaus]

Thank you! I have a follow-up question to this - while this may not be the best solution in regard to project roles, is there a way to grant every user the same access that allows them to create projects (only Kanban) with access to only certain fields (limited privileges, and NOT administrator rank)? I'm looking for a less structured solution than roles, as in this case every user needs to be able to create projects and boards.

Referring to your Step 1 above, would I just create a permission scheme that has everyone with the same permissions and apply across the organization?

I would like for everyone to have the capability in the screenshot below: