I have an user in vsts that need to use test manager.
In test manager the user need to create and change test plans and run tests too.
But I want to limit the access that this user have of taks.
Is it possible to block this user of viewing taks board?
Thank you
No, it's not possible for now.
If you added the user to your team project, he/she can view the task board.
I posted an user voice set permission for task board, you can vote and follow up.
Related
I run gitlab and activated mattermost. I created a new project and set up a mattermoast team.
Now I want to add all other users. But my user is no admin in mattermost. how can I solve that?
Thanks in advance.
According to this link, the first user in the system has the system_admin role.
Find the first user that is created on your Mattermost server and use it as an admin account.
We have an issue. User is in the Contributors group of the VSTS project. Able to view dashboard and work items. Unable to view Repos. Need help. Any suggestions?
User needed an MSDN license to use Visual Studio in addition to being in the correct group of the VSTS project. Trial license was not good enough.
According to your description, highly doubt those users only have Stakeholder access level.
People with Stakeholder access level could not commit their work on branch and unable to view repos.
Assign Stakeholder access to those users who need to enter bugs,
view backlogs, boards, charts, and dashboards, but who don't buy basic access. Stakeholders can also view releases and manage release
approvals. Stakeholder access is free.
Source Link: About access levels
See Stakeholder access for details of features available to stakeholders.
The user should have either Basic access or Visual Studio subscription which include code feature.
Moreover, if it's still not able to see any other projects after giving them those access. There is another concept called Permissions in Azure DevOps. Double check the permission for Contributor group.
Also make sure you have not add them to any other project team group expect the contribute group.
Once deny the Read permission for repos level, user will not be able to see the repos.
Read
Can read the contents of a file or folder. If a user has Read
permissions for a folder, the user can see the contents of the folder
and the properties of the files in it, even if the user does not have
permission to open the files.
We have a self-hosted gitlab solution and are trying to integrate a third-party application. For that we created a new account and wanted to set up a new application. But we were greeted by the following screen:
'Adding new applications is disabled in your GitLab instance. Please
contact your Gitlab administrator to get the permission'
I have an admin account and have looked everywhere to set this permission but can't find it. In my own account it is also impossible to add application, but in the admin area the possibility is there.
In the pricing table there does not seem to be any option that adds this feature so I don't think it is a blocked feature.
Any help would be much appreciated.
Go to https://gitlab.example.com/admin/application_settings
On the general tab beneath "Account and limit", there is a checkbox called "User OAuth applications".
Once you toggle this every user gets the ability to define her or his own OAuth2 Applications.
Is it possible to build and deploy an agent available only for some users , like for example a company, or limiting access ?
It depends on exactly what your needs are.
While not exactly what you are looking for, you can deploy an Action to Alpha test status. This lets you make it available to up to 20 users without going through the review process.
Additionally, you can deploy it to up to 200 users if you deploy to Beta. However, this still will require a review by the Action review team.
If you need more than this (and probably a wise idea even in other use cases), you'll need to use Google Sign in for Assistant or other identity methods to get the identity of the user and then determine if this is an authorized user as part of your Action. This will require review by the Action review team.
I've a requirement, where I need to add a few users from the UI. I'm working with "developer" access to the project in GitLab. Even if already a few users are added with different access while the project is created and only users added from the UI to perform developer role without making any changes in the project.
Is it possible and how to implement it?
"Overwriting" permissions is not possible and if you want to simulate this behavior you could create a new group and share this project with another group. Then you would need to deny access to individual group members. See this permission matrix.