Skip to content

Commit 239420c

Browse files
committed
Adding one new topic or admin guidance and several includes
1 parent 2a3567b commit 239420c

23 files changed

+615
-152
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
11+
## Add members to the Project Administrators group
12+
13+
The person who creates a project is automatically added as a member to the **Project Administrators** group. Members of this group have permissions to manage project configuration, repositories, pipeline resources, teams, and all project permissions.
14+
15+
It's always a good idea to have more than one person who has administrative privileges. To add a user to this group, see [Change permissions at the project level, Add members to the Project Collection Administrators group](../../organizations/security/change-project-level-permissions.md#add-members-to-the-project-administrators-group).
16+
17+
18+
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
## Add teams to scale your project
11+
12+
As your organization grows, we recommend that you add teams to scale your project. Each team gets [access to their own set of customizable Agile tools](../../organizations/settings/about-teams-and-settings.md).
13+
14+
![Agile tools and team assets](../../organizations/settings/media/agile-tools/agile-tools-team-assets-post-2018.png)
15+
16+
To learn more, see the following articles:
17+
18+
- [About projects and scaling your organization](../../organizations/projects/about-projects.md)
19+
- [Add a team, move from one default team to several teams](../../organizations/settings/add-teams.md)
20+
- [Add a team administrator](../../organizations/settings/add-team-administrator.md)
21+
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
## Add users to your project
11+
12+
You add users to a team or project so they can contribute to the team and project. Users can be added to multiple teams and projects.
13+
14+
Users that have been added to an organization, can easily be added to a project by adding them to a team or inviting them to contribute to a project.
15+
16+
Team administrators can add users to their team which automatically adds them to the project. By adding users to a team, you make team-specific tools aware of them, such as the team security group, Team Members widget, and sprint capacity planning tools. To learn more about teams, see [About teams and Agile tools](../../organizations/settings/about-teams-and-settings.md).
17+
18+
Members of the **Project Administrators** group can add users to a project. Adding users to a team or project automatically adds them to the project's **Contributors** group. Members of this group have permissions to most features needed to contribute to work items, code, builds, and releases. For an overview of default permissions, see [Default permissions quick reference](../../organizations/security/permissions-access.md).
19+
20+
Once users have been added to a project or organization, you can browse for their display name or user name (email alias) from any people-picker tool. Users can connect to a project and access features available through a supported client or the web portal.
21+
22+
To learn more, see the following articles:
23+
- [Add users or groups to a team or project](../../organizations/security/add-users-team-project.md)
24+
- [Manage your organization or project collection, Add users to your organization](../../user-guide/manage-organization-collection.md)
25+
- [Connect to a project](../../organizations/projects/connect-to-projects.md)
26+
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
## Define area and iteration paths to track work
11+
12+
If you support several products, you can assign work items by feature area by defining [area paths](../../organizations/settings/set-area-paths.md). To assign work items to specific time intervals, also known as sprints, you configure [iteration paths](../../organizations/settings/set-iteration-paths-sprints.md). To use the Scrum tools&mdash;sprint backlogs, taskboards, and team capacity&mdash;you need to configure several sprints. For an overview, see [About areas and iteration paths](../../organizations/settings/about-areas-iterations.md).
13+
14+
15+
> [!div class="mx-tdBreakAll"]
16+
> |Iterations| Areas |
17+
> |-------------|----------|
18+
> |![Default iterations, Scrum process](../../organizations/settings/media/areas/areas-iterations-iterations-intro-ts-2016.png) | ![A set of sample area paths](../../organizations/settings/media/areas/areas-iterations-areas-intro-ts-2016.png) |
19+
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
::: moniker range=">= azure-devops-2019"
11+
12+
## Remove unused services
13+
14+
To simplify the web portal user interface, you can disable select services. For example, if you use a project only to log bugs, then disable all services except for **Boards**.
15+
16+
This example shows that **Test Plans** is disabled:
17+
18+
> [!div class="mx-imgBorder"]
19+
> ![Disable a service](../../user-guide/media/services/set-service-visibility.png)
20+
21+
::: moniker-end
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
::: moniker range=">= tfs-2015"
11+
12+
## Install and manage extensions
13+
14+
An extension is an installable unit that adds new capabilities to your projects. Azure DevOps extensions support the following functions:
15+
16+
- Planning and tracking of work items, sprints, scrums, and so on
17+
- Build and release flows
18+
- Code testing and tracking
19+
- Collaboration among team members
20+
21+
::: moniker-end
22+
23+
::: moniker range=">= tfs-2017"
24+
25+
For example, to support [code search](../project/search/functional-code-search.md), install the [Code Search extension](https://marketplace.visualstudio.com/items?itemName=ms.vss-code-search).
26+
27+
::: moniker-end
28+
29+
::: moniker range=">= tfs-2015"
30+
31+
You want to tell your users about extensions and that they can [request an extension](../../marketplace/request-extensions.md). To install and manage extensions, you must be an organization Owner, a member of the Project Collection Administrators group. Or, you can get added to the [Manager role for extensions](../../marketplace/how-to/grant-permissions.md).
32+
33+
::: moniker-end
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
## Review and update notifications
11+
12+
A number of notifications are predefined for each project you add. Notifications are based on subscription rules. Subscriptions arise from the following areas:
13+
14+
- [Out-of-the-box or default subscriptions](../../notifications/oob-built-in-notifications.md).
15+
- [Team, organization, and collection-level notifications](../../notifications/manage-team-group-global-organization-notifications.md), managed by a team administrator or member of the Project Collection Administrators group.
16+
- Project notifications, managed by a member of the Project Administrators group.
17+
18+
If users believe they're getting too many notifications, direct them to [opt out of a subscription](../../notifications/manage-your-personal-notifications.md).
19+
20+
> [!div class="mx-imgBorder"]
21+
> ![Personal notifications](../../user-guide/media/services/personal-notifications.png)
22+
23+
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
ms.technology: devops-security
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 04/15/2021
7+
---
8+
9+
<!--- ability-to-find-user-once-added)] -->
10+
11+
> [!NOTE]
12+
> You may not be able to find a user from a permissions page or identity field if the user hasn't been added to the project&mdash;either by adding it to a security group or to a project team. Also, when a user is added to Azure Active Directory or Active Directory, there can be a delay between the time they are added to the project and when they are searchable from an identity field. The delay can be between 5 minutes to 7 days.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
ms.technology: devops-new-user
3+
ms.author: kaelli
4+
author: KathrynEE
5+
ms.topic: include
6+
ms.date: 02/25/2022
7+
---
8+
9+
10+
11+
::: moniker range=">= tfs-2015"
12+
13+
## Share your project vision
14+
15+
::: moniker-end
16+
17+
::: moniker range="azure-devops"
18+
19+
Each project has a summary page that's useful for sharing information through **README** files. Or, redirect users to a project Wiki. For users who are new to your project, we recommend that you [set up your project summary page](../../organizations/projects/project-vision-status.md) or [provision a Wiki](../project/wiki/wiki-create-repo.md). Use these features to share established processes and procedures for your project.
20+
21+
::: moniker-end
22+
23+
::: moniker range=">= tfs-2018 < azure-devops"
24+
Each project has a summary page that's useful for sharing information through **README files**. For users who are new to your project, we recommend that you [set up your project summary page](../../organizations/projects/project-vision-status.md). Or, you can [provision a Wiki](../project/wiki/wiki-create-repo.md). Use these features to share established processes and procedures for your project.
25+
26+
::: moniker-end
27+
28+
29+
::: moniker range=">= tfs-2015 < tfs-2018"
30+
Each project has a summary page that's useful for sharing information through **README files**. You can use this page to share information relevant to your project. To learn more, see [set up your project summary page](../../organizations/projects/project-vision-status.md).
31+
32+
::: moniker-end

docs/organizations/accounts/toc.yml

+6-5
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,22 @@
11
- name: About managing organizations
22
href: organization-management.md
3-
displayName:
43
- name: Plan your organizational structure
54
href: ../../user-guide/plan-your-azure-devops-org-structure.md?toc=/azure/devops/organizations/toc.json&bc=/azure/devops/organizations/breadcrumb/toc.json
65
displayName: projects, teams, repos, version control, scenarios, quantity, mapping, reporting, structure, data
76
- name: Create your organization
87
href: create-organization.md
8+
- name: Manage your organization
9+
href: ../../user-guide/manage-organization-collection.md?toc=/azure/devops/organizations/toc.json&bc=/azure/devops/organizations/breadcrumb/toc.json
910
displayName: new, project
1011
- name: Look up organization owner
1112
href: ../security/look-up-organization-owner.md
1213
displayName: access, permissions, owner, project collection administrator, valid
1314
- name: Add and manage banners
1415
href: ../settings/manage-banners.md
1516
displayName: add, update, remove, information, organization
17+
- name: Manage preview features
18+
href: ../../project/navigation/preview-features.md?toc=/azure/devops/organizations/toc.json&bc=/azure/devops/organizations/breadcrumb/toc.json
19+
displayName: set, enable, user, organization, features, pipelines, boards, repos, artifacts, test plans, dashboard, analytics, social, project
1620
- name: Adjust organization settings
1721
items:
1822
- name: Add privacy policy URL
@@ -30,11 +34,8 @@
3034
- name: Change organization Owner
3135
href: change-organization-ownership.md
3236
displayName: update, reassign, Project Collection Administrator, owner
33-
- name: Manage your organization
37+
- name: Rename or delete an organization
3438
items:
35-
- name: Manage preview features
36-
href: ../../project/navigation/preview-features.md?toc=/azure/devops/organizations/toc.json&bc=/azure/devops/organizations/breadcrumb/toc.json
37-
displayName: set, enable, user, organization, features, pipelines, boards, repos, artifacts, test plans, dashboard, analytics, social, project
3839
- name: Rename organization
3940
href: rename-organization.md
4041
displayName: owner, collection, administrator, new, name, Basic, URL, switch

docs/organizations/security/change-access-levels.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Change access levels for users or groups
2+
title: Add users or groups to an access level
33
titleSuffix: Azure DevOps
44
description: Learn how to set the access level for a user or group based on their license
55
ms.technology: devops-security
@@ -12,7 +12,7 @@ monikerRange: '<= azure-devops'
1212
ms.date: 06/02/2019
1313
---
1414

15-
# Change access levels for users or groups
15+
# Add users or groups to an access level
1616

1717
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1818

0 commit comments

Comments
 (0)