VSTS - Deny users to access another team backlog - visual-studio

I have 2 teams in my VSTS Project: Administrators and Developers.
I need to deny access to the Administrator Backlog to users inside of Developers.
Now any user has access to all teams backlogs and I can't find how to restrict this.
Anybody can help me?
Thanks!

The answer here works, but what do you do when you get 5 teams? 100 teams? For each team, do you Deny permissions to the other 99? Not very scalable. So I tried to find another way and figured out what I think is a better approach.
My goal, btw, was to create a good user-experience for my stakeholders, and constrain what they are able to access and modify. I personally feel that the members of the software engineering team should have access to and be able to contribute to any team... but that's personal opinion.
I got flummoxed, at first, by the fact that teams, when created, get added to Contributors... giving them access to all areas. So first, remove the Team security group from the Contributors group. Second, set the "View project-level information" permission to "Allow" for the team. Last, edit security for the top-level Area associated with the team (sub-areas inherit permissions), add the team group to security for that Area, and "Allow" the following for the team group
Edit work items in this node
View work items in this node
Manage test plans (if we want end-users involved in UAT work within Azure DevOps)
Manage test suites (same)
This assumes, btw, that you've also assigned the top-level Area for that group to that team, and included sub-areas.
At this point, as a member of a team, a stakeholder will only see the teams they are members of, under "My Teams", when viewing boards, backlogs, and sprints. They could go out of their way to browse any other board... but they wouldn't see anything because they don't have permissions to the items on those boards.
Then, I would assign the various stakeholders to the team(s) in which they had a stake.
One could also add software engineering members to teams as well, as this uses an "Allow" approach instead of a "Deny" approach, and so their "My Teams" list would include teams they were members of. Personally, I'd probably go with allowing the engineers to control it themselves through "favorites", rather than having to administer adding \ removing engineers from team security groups.

You can restrict the team users with Area Security.
Follow below steps to achieve that:
Create 2 Groups for the 2 teams: (Admin -> Security -> Create Group)
e.g.: AdminGP for Administrators team, DevGP for Developers
team.
Add the team users to the corresponding Group.
Navigate to Home project, then create Areas for each Team if no
areas created before. (Admin -> Work -> Areas)
e.g. TeamAdmin and TeamDev in below screenshot
Navigate to the specific Team, and set the default Area path for
the team.
Back to home project, Admin -> Work -> Areas, Right click the
AdminGP area -> Security
Add the corresponding Groups for the teams, then set bellow
permissions for TeamDev Group (Developers team):
View permissions for this node - Deny
View work items in this node - Deny
Thus the members in Developers team cannot see the Administrators team's work items in Backlog/Board.

Related

How can I easily add others to update my G Suite App listing?

I've looked all over the admin console, but can't find where to add other users so that they can edit our listing. Can you please provide a URL/link to where I should navigate?
You may want to check this support page. You can:
assign pre-built roles for performing common business tasks
assign custom roles you create for your organization
assign more than one role to a user to grant all privileges in those roles
Be noted that you must be signed in as a super administrator for this task.
The user typically gets their new privileges within a few minutes. However, it can take up to 24 hours. When they sign in to their account, they arrive at the Admin console dashboard. Here they see the controls allowed by their privileges.
Hope this helps!
I think you want to navigate to this URL while logged in as the app project owner:
https://console.cloud.google.com/iam-admin/iam/project?project=(add your project ID)
And assign roles to different users or groups.
you can use group publishing on the gsuite marketplace:
Set up Group Publishing
You can share ownership of your items in Google Chrome Web Store with other developers by setting up group publishing. With group publishing, you can add developers to a Google Group, who can then act on your behalf. They'll have access to all the items you own and can make any changes to them that you can make.
https://developer.chrome.com/webstore/publish#set-up-group-publishing
(each member of the group should pay the 5$ developer fee though.)
You can configure the group from your webstore dashboard.
https://chrome.google.com/webstore/developer/dashboard

TFS 2013 - Can I restrict a user to access only a sub-area in a project?

I have a user requesting that an employee be allowed to access only a specific sub-area in a project.
No access to the source code, no access to tests, only access to a single "area".
I have tried granting the user access as a Reader, and then setting specific security permissions on the area node. The business complains that the user has access to everything.
Is this possible to accomplish with the TFS 2013 security model?
Not trivial, the solution goes along this line.
Remove from the individual any groups except "Valid Users".
The user account must have "View project-level information".
Give the individual "View work items in this node" by right-clicking on the Area node he/she must have access.
You can add additional permission in this latter, if the person requires write access.
Define a new TFS group for these "special users".
Click on the Group Membership. This should open up the web page in IE.
Now click on the link "Create TFS Group" on the top left hand side.
Create a new TFS group for these special users. Lets call it "Special Users".
Remove the UserID of these special users from any other TFS groups that they are present.
Go to the specific sub-area in the project which they need access to. 1. Right click the file -> Advanced -> Security
Now here you can define the rights for your new "Special users group". Give them just the read access and deny everything else.

Joomla 3: Permission to manage users and nothing else

I'm developing a Joomla 3 website, where registered users can belong to several groups of interests (music, theater, technology, and so on).
I would like to give permission to my client to edit users by placing them in groups he desired. For example: user 1 can be in music and theater group; user 2 just registered (no group) and user 3 in technology group. Unfortunately the only permission that Joomla 3 allows you to edit users is the Administrator, but if I give this permission to my client, he will be able to edit articles, themes and other features that I do not want it to edit.
How can I create an access level that can manage only users list?
Thank you and sorry about my english.
Create a new group, assign that group only permission for managing users and whatever else you want and assign your users to that group but not admin.
As a short answer, if you don't want you client to be administrator, you can assign him to the manager user-group.
Then go into the Users Manager Component and click the Options button to go into its configuration page.
There you can override the Permissions Settings for the Users Manager component, so the Managers users will be allowed to Access Administration Interface of the component.
You will have the change the respective setting from inherit to allowed.
Of course if needed, you can create a complete custom ACL, with special usergroups for your users that will have certain accessibility and permissions.
But be careful, because ACL sometimes can be confusing and you might end up with a total mess.

How to restrict access to dashboards by user/group permissions?

We develop software for different customers and use a single instance sonarqube. We have created one dashboard per customer which contains all its projects.
Up to now just our developers used the system and everything was fine.
Now we would like to give our customers access to sonarqube so they can see their projects state.
We put the customer users in diffrent groups and restricted access to the projects by group. So each customer can only see his projects. Still fine.
But we did not find a way to restrict access to the dashboards. So each customer can see the list of alle available dashboards. This contains the list of all our other customers. How bad! Just to make it clear: For a customer user the list of projects of all dashboards except its own company dashboard will be empty - he just sees the names of the other customer, which is still to much.
So is there any solution to configure dashboard visibility by users/groups?
I do confirm that this is not possible to share a dashboard only with some users or groups. When sharing a dashboard, you share it with all users.

Laravel > Cartalyst > Sentry add remove permissions at runtime

My Understandings
I know we can add Group with some permissions and then we can create users with some permissions and finally we can add users to multiple permissions Groups. We can call these groups as roles as well. This is fairly simple.
The Real Problem
suppose we have teams and team members modules. A user "abc" is a member of multiple teams A, B, C. In team A the user's role is TeamLead. In team B his role is Assistant and in team C his role is NormalMember.
Now the problem is every one can see the list of teams. We need to display the Edit and Delete icons against each team. but only the authorise user can see the edit or delete link based on their role in the team inside a loop.
This is something linked with adding/removing roles or permissions on the fly.
Do you have any idea that how can I achieve this? how can I check permissions inside a loop with different roles in different teams.
Thanks in advance.
regards.
you can check whether the group is assigned to the user and accordingly show the buttons
Also use has_access attribute of sentry while defining route. In this case you can limiting the access of route itself if user try to access edit or delete functionality through url

Resources