Hi there,
I want to add a new user and only for this specific project.
When I tried to add this new user, the default access is this user has access to all the projects, I have read this article on how to setup the new user for specific project but I don't understand how the implementation really works.
The article mentioned about setting up the project role, the group user and also modifying the permission to the group/role, this part that I don't understand on how to setup the permission to only see this one project and also only for this group.
So the condition is:
1. My company has this vendor that manage to handle some of our projects.
2. The team of this vendor handle each of our project.
3. The goal that we want is to limiting this each member (developer) of the vendor to only has access to each project, not all the project that the vendor given.
The question is should I create a group for each project and adding the new user to each group for the project or can I create just 1 group for external-jira-software-access and decide who will be have access to each project.
So this is what I have been done this far:
1. I have created this new group as external-jira-software-access
2. Added the new user to that group and removed the user from other default group
3. Create a Project Role that named External team
I don't know the next step that I need to do to achieve the goal, can anyone help me to clarify this confusion that I experiencing right now?
Thank you guys in advance!
Oh by the way,
This is the link for the article that I tried to follow but I don't understand:
Maybe if anyone has any easier way to help me through this situation, please let me know guys
Anyone else has another option that I can try or maybe wants to help to explain how to do it?
I still stuck with this issue.
Any help is appreciated.
Thanks guys.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dewa Fakha Shiva Yes you are in right track. But remember, let the Atlassian-addons-project-access and atlassian-administrator be there. This will mess other roles.
Remove any logged in users, if you donot one everyone to view the project/tickets.
Then click update and add either that particular user or a particular group whom you want your project to be accessible.
You do not need to worry. Just copy this Permission scheme and play around with that scheme. Make it final. Meanwhile create a separate demo project as your playground. Apply that permission scheme which you just copied and modified to your demo Project. Give it to test with the people who should be seeing and who shouldn't have access to.
Finally apply the updated Scheme to your real project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was added the new user to the group and removed all other permission like addons and administrator, but after you said so, I created another permission scheme and only delete the any logged in users, but there is nothing change, I can still see all the other projects.
Is there anything I do wrong?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To keep it simple, a normal developer in your team, Jira user must have basic permission of viewing a ticket, editing and assigning it to another team member. Few permissions like managing sprints, providing roled and permissions are limited to Scrum Master, Project Manager and Jira Administrators.
So one of the simple way to moderate user to only browse a single project is managing the Permission Scheme.
What you can do is you can copy the existing Default Permission scheme that you can find in your project Setting -> Permission section. In that permission section, remove unwanted users or groups from the permission you don't want to allow. And add individuals or groups in individual action like Edit, Comment, Delete, Assign, etc.
The challenge here is:- We can easily restrict an individual from one project. But if you have multiple project, then there are two ways:
1. Either create separate permission for each project, divide project based group and provide access to those groups only.
2. Otherwise say one team member can only view and moderate one project. But the other project permission still allow basic view and edit permission to users in jira-users, jira-developers group. So they will be able to view rest of the groups.
Choice is yours to implement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sanjog,
Thank you for your response.
I still have this confusion about how to manage the permission that only allowing the specific group to have this access to only one project.
So I should removing all of this and adding only 1 group to every section in here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried to remove all of these and only added the group that I created, but nothing works, I still can see other projects that I'm not suppose to see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you apply restriction to individual projects making different permission scheme and assigning unique permission scheme to individual project?
Like I mentioned earlier,
In default permission scheme Jira-users, jira-developers are provided permission to view and update tickets. So if you fall under jira-user or jire-developer and Any Logged In User, you can definitely browse other projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I'm not mistaken about what you meant, I applied the restriction to the group I created and in that group, there is only 1 user that I added.
Here is the detail of the user that I added to the group.
So is this means that I don't in the jira-user or jira-developer permission?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If that one user in your TCA group is also in default groups like jira-developers and jira-users, they can view other projects.
Please restrict users in limited group and provide access to your group to the permission that the user should perform.
Its a combination of Jira groups/ permission scheme and mapping of permission and which user or group should be enabled to perform those actions.
Thank You.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How to check if that one user not in default group like jira-developers and jira-users?
I only know the one that I sent you, so I think if it is only in the TCA group, so it means that the user will only be in the TCA group, not any other group like default group from Jira.
1. I think I already setting up the user only to TCA group
2. The TCA group is added in the permission scheme and I deleted the any logged in user in that one permission scheme that I binded to the TCA group
Anything that missed that I needed to do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.