Jira's user permission system is far more flexible than just having a "user type"
In some of my client systems, I'm an adminstrator, so you'd think I have "full access". I do. To adminstrative functions. I have no access to the projects or issues. As an admin, I can give myself that access, but my admin rights have nothing to do with my project rights. "Full access" in the way you're probably thinking of it is not implemented in Jira, which is a good thing, because it's a dreadful access model.
I tend to try to separate out "admin" rights from "project" rights. Admin rights are two-level - system admins can change anything, and Jira admins have less power, in that they can only change the way Jira behaves to the users.
Project rights are far more complex (because they're flexible) and depend entirely on the permissions you give on a user, or role, or group, basis. I can be a developer in two projects, and have different rights to each project. It all depends on the permission scheme for the project.
So the answer to "what level of access does a user have" is "whatever you have granted them in your permissions"
It all depends on how you configure your instance...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs