In all the forums I've read you have to do the following things to create client specific projects (and to let them see ONLY this project):
1. Create a client group
2. Create a project role for the client
3. Copy the default permission scheme to create a client scheme
4. 'Grant' the client project role the ability to 'Browse'
5. Add client roles to the project
6. Use the client permission scheme to the project you want the client to see
This does not make sense and when I log in as the 'client' I am able to see all the projects and NOT the project I wanted to see... please help!
Ok, so you have the permission scheme. It says - Browse Projects - Granted to Project Role - Users.
You have to then go to the project, edit it and look at the users and roles tab. You'll see who the group "users" are.
In my case, Users, are Jira-Users, and everyone is in Jira-Users, so the project is visible.
If you want to change that, on the project security level, remove jira-users from users and click add users to a role. Select the group or users you want to add to Users and done.
Thanks Greg, I have all of that set up and something still isn't right.
I've set the permission scheme to the client project and when I log in as a client I can see every project EXCEPT the one I want. That one seems to disappear.
What is the correlation or flow for Projects/Permission Scheme/Project Role/Group?
What groups is that user a member of?
For flow - Permission Schemes define what can happen on the Project level.
What may help you visualize this better is the permissions helper tool.
How to use the permissions helper
1. Click the settings cog wheel (upper right), and select Issues.
2. Click Permission schemes.
3. Click Permission helper.
4. Enter the following details:
a. The name of the user having issues with project permissions
b. The issue key that the user doesn't seem to have access
c. The project permission that you want to check against user's current permissions
The Permission helper dialog will display the status, summary, and details of the project and issue permissions set for the specified user, as well as any failed condition
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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