nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I create a read-only user

George Carvill

I want to create a user called "Viewer" with a password who will only be able to read Issues, not change anything.

I have done so. Have put him in a Group called "Viewers."

In the test project, the user has these permissions:

*Browe Projects

*View Workflow

In my test project, the viewer is assigned to the "Viewers" project role.

But when I try to log in as "viewer" I am told I don't have permission.

Accepted answers

Nic Brough -Adaptavist-

You say "the user has these permissions"

That's a little too simple, as you don't explain exactly how they get these permissions. It is a two layered thing and you need to be clear to follow it through.

From first principles, could you go back into the system as Admin and then

Go to the project
Check the permission scheme is correctly associated with the project.
Open the permission scheme (directly from the project)
Look at the "browse" permission. List everything in there (e.g. Role:developer, Group:fred, Assignee)
Now go back to the user and look at their Roles and Groups

One other test too - edit the browse permission and explicitly add "user: viewer" and re-test it.

Finally, are you using "security levels" at all?

All comments

Nic Brough -Adaptavist-

You say "the user has these permissions"

That's a little too simple, as you don't explain exactly how they get these permissions. It is a two layered thing and you need to be clear to follow it through.

From first principles, could you go back into the system as Admin and then

Go to the project
Check the permission scheme is correctly associated with the project.
Open the permission scheme (directly from the project)
Look at the "browse" permission. List everything in there (e.g. Role:developer, Group:fred, Assignee)
Now go back to the user and look at their Roles and Groups

One other test too - edit the browse permission and explicitly add "user: viewer" and re-test it.

Finally, are you using "security levels" at all?

George Carvill

From first principles, could you go back into the system as Admin and then
Go to the project
Check the permission scheme is correctly associated with the project.

>> Default Permission Scheme is assigned

Open the permission scheme (directly from the project)
Look at the "browse" permission. List everything in there (e.g. Roleeveloper, Group:fred, Assignee)

>> Project Role(users), several groups, and the Single User (viewer)

Now go back to the user and look at their Roles and Groups

>> The user "viewer" is a member of the Group "Viewers"

One other test too - edit the browse permission and explicitly add "user: viewer" and re-test it.

>> Done, as you can see above

Finally, are you using "security levels" at all?

>> Dunno. I don't see any other settings than Issue permission

Nic Brough -Adaptavist-

Ok, the second line makes the groups and roles irrelevant - "single user (viewer)" should make the issue visible to that user. So you're definitely logging in as that user and it's not seeing the issue?

On the security levels, go back to the project administration and look at the tab below "permissions" where you set the permission scheme. On that tab, does it say "Issue security is currently not enabled for this project." or something else? (Or does the tab not appear at all?)

George Carvill

So you're definitely logging in as that user and it's not seeing the issue?

No. The problem is that when I try to log in I get this message:

You do not have a permission to log in. If you think this is incorrect, please contact your JIRA administrators.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

read-only