I have a user who is both Project Admin and Team Admin (all teams) within a project in Azure DevOps. They appear to be unrestricted within the project except when they attempt to modify sprint taskboard settings. They are immediately presented with a warning:
'You do not have sufficient permissions to configure cards for this
team. You must either be a team administrator or a project
administrator.'
As the user is both project/team admin and able to modify the project's process, I'm at a loss as to what is missing. Or could this possibly be a bug? This is the only thing within the project that is blocking the user.
The screen is under 'Boards/Sprints/[Sprint Name]/[Cog icon in top right]'
The access level of this user is stakeholder. Please contact members of the Project Collection Administrators group to change the access level of the user to Basic.
Users with Stakeholder access level have partial access to Azure Boards in private projects. You can find more detailed information about access level in this document.
Related
I want to add a group/user to an Azure DevOps project with just access to repositories and pipelines.
If I deny "View project-level information" they don't have access to the project at all.
If I allow the "View project-level information" it gives them a read-only access to the Project Settings including permissions to see users and members of other groups etc.
It seems unbelievable that such a basic security and privacy hole exists.
Am I missing something in the config because I have never seen this in any other application and I find it hard to believe that everyone else using Azure DevOps finds this acceptable.
The easiest equivalent is GitHub (that Microsoft now owns) and you can't see the project settings if you are just a contributor.
How do I give external contractors access to the project to work but prevent them from viewing the Project Settings?
There is no possibility to restrict access to the Team Project - Project Settings page. The only thing that comes close is the feature that is now in preview: Limit user visibility and collaboration to specific projects, which will enable you to restrict access to the Organization Settings. You could suggest this feature in the Microsoft Developer Community.
I have added multiple team members to two different teams in Azure Devops project. But team members are not able to see organization, project and dashboards when they login to devops account?
team members are not able to see organization, project and dashboards
Users cannot see the organization, you can first check whether these users have been added to the organization in Users of Organization Settings.
Then you can check whether the user has the permission to access the project on the Manage user page.
Regarding that users cannot see the projects, you can check whether the “View project-level information” permission of the team is set to Deny in the Permissions of Projects Settings.
Regarding that the user cannot see the dashboard, there should be no permission to restrict it. All users in the project should be able to see the dashboard. Can you share the screenshots about this issue?
In addition, you can try to let users log in with incognito window to see if the problem exists. Check if your organization is connected to AAD.
This is the answer for my additional questinos.
To get an access to Devops project user must be added in the organization either as stakeholder or owner
Once they are owner or stakeholder they are able to access all the features.
My Account(AAD) is Linked with 2 DevOps Organisation(personal organization & Business orgnaization)
I am unable to view Business orgnaization on DevOps Profile but able view personal organization.
I am able to access both via Url https://dev.azure.com/xxxCloud/.
I can't able to Connect DevOps Business Organisation with Visual Studio also.
Please try the following steps:
Please enter aka.ms/vssignout in browser and login to aka.ms/vsprofile again to see if the issue still exists.
If your organizations are in different AADs, please select the right directory in the dropdown list.
Please use other PCs to sign in and check if it works.
If you sign in this organization, can you see the projects in it? Please click specific projects in Web UI, or add project name in organization URL to get access to it.
Please ask your AAD admin to remove your MSA account from Azure Active directory and re-add you again to check if the issue still exists.
I need some of my users to see/update only the boards others to see Repos, others to see the Pipelines only. Is there a way to set such permissions?
I couldn't find any default permission that does this
The lowest access level we can give is stakeholder and set users as Project Reader, this makes Repos invisible at most.Users can still see Boards and Pipelines,but without permission to update.
If you don't want some users to see Repos, then you can set the access level of these users to Stakeholder, and then check the project in Manage projects that you want the user to enter, so that these users can only see Boards and Pipelines without Repos in the project. Note:Make sure that the project you want these users to enter is a private project.
You can also set up the following settings to make the content in Repos inaccessible.
Setting: Project Settings -> Repos Repositories ->select the users or groups which you want to set permission -> change the Read permission to Deny
In addition you can make the build pipeline and release pipeline in the Pipelines service invisible to the specified users.
Settings: Pipelines Builds -> Click "⋮" choose Security -> select the users or groups you want to set permissions -> Change the View build pipeline permission to Deny
The same setting in Releases can make the release pipeline invisible.
Hope this helps.
I am using Visual Studio Team Services.
Part of Release Management is allowing users to approve a deployment environment or not. I have noticed that the list of approvers can only be of people added to VSTS. Is it possible to have approvers who are not added to VSTS.
I want to have the tracking of their inputs for approving, but they don't have any interest in seeing user stories, source code, etc.
If you don't want people to have access to work items and source code, restrict their access by defining security groups and adding them to these groups.
Yes — they will need at least a basic licence.
You can add the specific approver with a basic licence, then use the security settings to add them to either the approver group or give them specifically approval rights. (More info.)
You can also specify account (user) groups as approvers. When a group is specified as an approver, only one of the users in that group needs to approve in order for the release to move forward. If you are using Visual Studio Team Services, you can use local groups managed in Team Services or Azure Active Directory (AAD) groups if they have been added into Team Services. If you are using Team Foundation Server (TFS), you can use local groups managed in TFS or Active Directory (AD) groups if they have been added into TFS.