You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the majority of features and functional tasks are managed by [individual permissions](about-permissions.md), there are several artifacts and features that the system manages through role-based permissions. You can add users or groups to a role. Each role determines the set of operations that the user can perform as described in the following sections.
19
+
Security for both build and release pipelines, and task groups, is managed using [task-based permissions](about-permissions.md). Several pipeline resources have their security managed through role-based permissions. Roles can be assigned to users or groups. Each role determines the set of operations that a user can perform, as described in the following sections.
20
20
21
-
Many role-based permissions can be set for all artifacts of a specific type in a project, or for the project or collection and then selectively inherited for a specific artifact. Role memberships for individual items automatically inherit those set for the project or collection. If required, you can turn off Inheritance for a specific artifact.
21
+
Role-based permissions are set for all resources of a specific type in a project or in an organization or collection. Individual resources inherit the permissions from the project-level settings. Inheritance can be turned off for an individual artifact if necessary.
22
22
23
23
24
24
## Default role assignments
25
25
26
-
By default, all contributors in a project are members of the User role on each hosted queue. This allows every contributor in a project to author and run build and release pipelines using hosted queues.
26
+
By default, all contributors in a project are members of the User role on each hosted queue. This role allows every contributor in a project to author and run build and release pipelines using hosted queues.
27
27
28
28
<aid="agent-queue-security-roles"></a>
29
29
30
30
## Agent pool security roles, project-level
31
31
32
-
You [add users to the following security roles](../../pipelines/policies/set-permissions.md) from the project-level admin context, **Agent Pools** page. For information on adding and managing agent pools, see [Agent pools](../../pipelines/agents/pools-queues.md).
32
+
You [add users to the following security roles](../../pipelines/policies/agent-pool-permissions.md) from the project-level admin context, **Agent Pools** page. For information on adding and managing agent pools, see [Agent pools](../../pipelines/agents/pools-queues.md).
33
33
34
34
[!INCLUDE [temp](includes/agent-queue-roles.md)]
35
35
36
36
<aid="agent-pool-security-roles"></a>
37
37
38
38
## Agent pool security roles, organization or collection-level
39
39
40
-
You [add users to the following security roles](../../pipelines/policies/set-permissions.md) from the **Organization settings** or collection-level admin settings, **Agent Pools** page. For information on adding and managing agent pools, see [Agent pools](../../pipelines/agents/pools-queues.md).
40
+
You [add users to the following security roles](../../pipelines/policies/agent-pool-permissions.md) from the **Organization settings** or collection-level admin settings, **Agent Pools** page. For information on adding and managing agent pools, see [Agent pools](../../pipelines/agents/pools-queues.md).
41
41
42
42
[!INCLUDE [temp](includes/agent-pool-roles.md)]
43
43
44
44
## Deployment group security roles
45
45
46
-
You [add users to the following roles](../../pipelines/policies/set-permissions.md) from **Pipelines** or **Build and Release**. For information on adding and managing deployment groups, see [Deployment groups](../../pipelines/release/deployment-groups/index.md).
46
+
You [add users to the following roles](../../pipelines/policies/deployment-group-permissions.md) from **Pipelines** or **Build and Release**. For information on adding and managing deployment groups, see [Deployment groups](../../pipelines/release/deployment-groups/index.md).
You [add users to the following roles](../../pipelines/policies/set-permissions.md) from the collection-level admin context, **Deployment Pools** page. To create and manage deployment pools, see [Deployment groups](../../pipelines/release/deployment-groups/index.md).
52
+
You [add users to the following roles](../../pipelines/policies/deployment-group-permissions.md) from the collection-level admin context, **Deployment Pools** page. To create and manage deployment pools, see [Deployment groups](../../pipelines/release/deployment-groups/index.md).
## Library asset security roles: Variable groups and secure files
59
59
60
-
You [add users to a library role](../../pipelines/policies/set-permissions.md) from **Pipelines** or **Build and Release**. To learn more about using these library assets, see [Variable groups](../../pipelines/library/variable-groups.md) and [Secure files](../../pipelines/library/secure-files.md)
60
+
You [add users to a library role](../../pipelines/policies/library-permissions.md) from **Pipelines** or **Build and Release**. To learn more about using these library assets, see [Variable groups](../../pipelines/library/variable-groups.md) and [Secure files](../../pipelines/library/secure-files.md).
61
61
62
62
[!INCLUDE [temp](includes/library-roles.md)]
63
63
64
64
<aid="service-endpoint-roles"></a>
65
65
66
66
## Service connection security roles
67
67
68
-
You [add users to the following roles](../../pipelines/policies/set-permissions.md) from the project-level admin context, **Services** page. To create and manage these resources, see [Service connections for build and release](../../pipelines/library/service-endpoints.md).
68
+
You [add users to the following roles](../../pipelines/policies/service-connection-permissions.md) from the project-level admin context, **Services** page. To create and manage these resources, see [Service connections for build and release](../../pipelines/library/service-endpoints.md).
@@ -184,7 +184,7 @@ We encrypt data via HTTPS and SSL to help ensure that it isn't intercepted or mo
184
184
- Azure Blob Storage connections are encrypted to help protect your data in transit. For data at rest stored in Azure Blob Storage, Azure DevOps uses [service-side encryption](/azure/storage/common/storage-service-encryption).
185
185
186
186
> [!NOTE]
187
-
> Azure DevOps is not Federal Information Processing Standards (FIPS) 140-2 or 140-3 compliant.
187
+
> Azure DevOps is Federal Information Processing Standards (FIPS) 140-2 or 140-3 compliant.
188
188
189
189
The Azure DevOps team uses the Azure infrastructure to log and monitor key aspects of the service. Logging and monitoring help ensure that activities within the service are legitimate, and they help detect breaches or attempted breaches.
To determine the effective permissions of users and groups for a release, you can download the permissions report. Requesting the report generates an email with a link to download the report. The report lists the effective permissions for the release you select, for each user and group specified at the time the report is generated. Inherited permissions come from a parent group which you can view from the web portal. The report is a json-formatted report that you can open using Power BI or other json reader.
18
+
To determine the effective permissions of users and groups for a release, you can download the permissions report. Requesting the report generates an email with a link to download the report. The report lists the effective permissions for the release you select, for each user and group specified at the time the report is generated. Inherited permissions come from a parent group that you can view from the web portal. The report is a json-formatted report that you can open using Power BI or other json reader.
19
19
20
20
You can also use the [Permissions Report REST API](/rest/api/azure/devops/permissionsreport/?view=azure-devops-rest-6.1&preserve-view=true) to download the report.
21
21
22
22
## Prerequisites
23
23
24
-
- To download the permissions report, you must be a member of the **Project Collection Administrators** group. The user interface button won't appear for users who aren't a member of this group.
24
+
- To download the permissions report, you must be a member of the **Project Collection Administrators** group. The user interface button doesn't appear for users who aren't a member of this group.
25
25
26
26
To find a member of the **Project Collection Administrators** group, see [Look up a project collection administrator](look-up-project-collection-administrators.md).
27
27
@@ -53,7 +53,7 @@ You can download the report for a specific release from the release's Security d
53
53
54
54
## Related articles
55
55
56
-
-[Set different levels of pipeline permissions](../../pipelines/policies/permissions.md)
56
+
-[Set different levels of pipeline permissions](../../pipelines/policies/pipeline-permissions.md)
57
57
-[Manage permissions with command line tool](manage-tokens-namespaces.md)
0 commit comments