User seems to not have any permissions

Oliver Mueller

I setup a user an made sure he has permissions to browse the project issues:

1.He is part of a group that I added in the permission scheme asocciated with the project in question

2.He has the project roles: User & Developer

when I try to login with the user account, I get an empty Dashboard page with the message:

"This dashboard does not contain any gadgets or you do not have permission to view them. Perhaps you need to log in to see them."

I used the permission helper for the user and here everything seems to be fine:

	Group XYZ is in the extern group
	Project Role XYZ is a member of these project roles: Developers, Users

Oliver Mueller

finally found out what was amiss: my group was not added to the jira users in the global permissions page.

Mick Nassette had the answere:

Mick Nassette [Atlassian] added a comment - 20/Mar/13 11:06 AM

Hi Oliver,
There are 2 ways to accomplish this. First of all, you can define user permissions though the permission schemes tied to the specific project. Often, the permissions are assigned based on project role. You can assign individual users or user groups to project roles.

Currently, it is likely that any newly created users, are receiving permissions in different projects due to the fact that the group "users" has been assigned to project roles in these projects.

Therefor, one solution would be to remove this group (or any other relevant groups to this user/project) from the project roles in the projects where the specific user is not supposed to have access to. Essentially, you will only have to apply this to the "Browse Projects" permission, since this locks out any other actions. This solution however requires you to go through all your projects in order to get them properly configured. Though this can be a lot of work, when your instance is growing and is getting more and more projects and users, this solution scales best in such a scenario. So though it might be more work now, it might save for in the future.

The second solution would be as follows: Create the user. Create a group. Add the user to the newly created group and remove it from all other groups. Add the group to the JIRA Users permission under your global permissions. Configure the permission scheme of the relevant project according to your wishes. Opposed to the first solution, this requires less work to set up for 1 or a few projects, but it scales badly when your instance grows. It will especially become rather hard to configure and maintain when you are getting users which require overlapping permissions in various projects.

I hope either of the 2 provided solutions are to your requirements, if you need additional assistance, please let me know.
Cheers,
Mick