don.glasco please see my previous comment. Unfortunately we have no plans to improve Create Shared Objects permission granularity at this time.

Regards,
JIRA Agile Team

I see that this issue is 'Resolved', but there is no way to limit permission to create Agile board but still allow one to create shared filters and dashboards

Never mind my previous comment. They don't have permissions to create boards, but they still can see the option there, which is not as bad, but it's not the ideal solution.

Michael regarding what you are saying in your comment:

"With regards to the original request of restricting the creation of Agile Boards, you can achieve this today by restricting the users who have the global permission "Create Shared Objects". If a user does not have this permission then they will be unable to create a new Agile Board."

I have a group a group of users that doesn't have this permission and they still can create boards. The only global permission that this group has is "JIRA Users". Do you know what might be happening?

With regards to the original request of restricting the creation of Agile Boards, you can achieve this today by restricting the users who have the global permission "Create Shared Objects". If a user does not have this permission then they will be unable to create a new Agile Board.

Access to viewing Agile Boards at all is something we may address in the future, however to simplify things let's not keep this issue open for that purpose.

Regards,
JIRA Agile Team

You can only manage your own boards though.

Ranking is controlled by the Schedule Issues permission, so you can limit access to that.
Creating sprints and adding to them is controlled by the Project Administrator role, so you can limit access to that.

My main concern is that anyone can create their own boards. I'd like to have that ability locked down somehow.

We have had sprints modified by users and fear the day someone accesses manage boards and deletes one!

We are facing the same problem in our company.
We currently use JIRA+GH only for development.
We would like to expose JIRA as our ticketing system, but we would not like our customers to have access to the boards.
In the best case it would be possible to define for the customer to see only dashboard and tasks.

In my ideal world, there would be more Global permissions regarding Greenhopper, like "Greenhopper administrators" and "Greenhopper users", and I could assign these permissions to specific groups.

I would like to urge Atlassian to consider this simple change which has been reported as early as august 2009 (see GHS-1374).

A simple solution would be to introduce a user group "Greenhopper users" that would allow or deny access to all Greenhopper functionality.

Please note that this request has nothing to do with licencing.