TF14044: Access Denied: User needs the AdminWorkspaces global permission(s)
I am part of a small DevOps team who are migrated to Azure DevOps. Recently we got another two new members joining, however when they connect to the TFS, they received the following error: TF14044: Access Denied: User <X> needs the AdminWorkspaces global permission(s)
Since I got access to TFS, I run the command tf permission, and it returns with the result my username have no global permission explicitly set. As I am able to access TFS but the two new members cannot, what should I do?
Add Comment
I had the original issue here when trying to map a workspace. I added "Allow" to the Administer Workspaces.
When I tested again, it gives me a different error now
"Access Denied: xxxx xxxx needs the following permission(s) in the Identity security namespace to perform this action: Manage group membership. Additional details: security token: bafa93ab-8717-4a8d-988f-4692fd2bc5bc\195e224a-5f7e-4402-8bc7-de99501447a7, permission bits required: 8."
It seems like you don't set "Manage group membership" permission. We’d recommend you create a new ticket so that we can investigate this issue further. Thank you for your understanding.: )
We appreciate you taking the time to report this problem. We will not be able to investigate this one immediately. We know this problem is important to you, so we will continue to monitor it.
Solution by
Thank you for your feedback! How did you add your new user to a project team? Which access level this user in? Could you please check whether your new users has "Administer workspaces" permission in collection security page ( just input the user's name in the Filter users and groups box, you can see all the permission under this user)? We look forward to hearing from you!
Add Comment
Hello!
Here we have the same problem, but unlike the permission "Allow" is "checked", the user cannot create an workspace.
Any other solution?
Could you please set this user has "Administer workspaces" permission? We’d recommend you create a new ticket so that we can investigate this issue further. Thank you for your understanding.: )
Solution by
Add Comment
Hi Johnny, could you please go to Edit Workspace page, click advanced, check what’s the permissions of your workspace, Public or private? By default, a workspace is private which means that only the owner can access it. You can try to make the workspace public so other users can access it.
Tracy, thank you for your reply. I tried to edit the workspace, giving Public workspace (limited) permission, and the problem is still there. By chance I tried to create a shelveset but was presented with another error: TF14075. Note that the developer is the local administrator. Could this be only resolved by uninstalling and cleaning former Visual Studio installation?
Solution by
@
Adimar Nossol and @ Johnny Hadryanto I have done all the permission setting as suggested above However the problem is still same, We are using VS 2017 community version.
