Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
This article describes how to set and manage permissions for your team project wiki and project README files. By default, all members of the Contributors group have permission to edit wiki pages.
Manage permissions for wikis
By default, all project Contributors have "read" and "edit" access to the Git repository for the project wiki. You can manage these permissions and control who can read and edit wiki pages. For more information, see Get started with permissions, access, and security groups.
Sign in to your project (
https://dev.azure.com/<Organization>/<Project>
) in Azure DevOps.Select Project settings.
Under Repos, select Repositories.
Select the wiki repository, typically named
<ProjectName>.wiki
.Select the Security tab to manage permissions for the wiki repository.
The Security tab displays a list of users and groups with their current permissions. You can modify permissions for existing users/groups.
For definitions of each repository permission, see Git repository (object-level) permissions.
Note
If you don't have access to create a wiki page, you can request access from a project Administrator. They can grant you adequate permission on the underlying Git repository for the wiki.
Grant Edit permissions to an individual or group
To grant Edit permissions to an individual or group, complete the following steps:
Sign in to your project (
https://dev.azure.com/<Organization>/<Project>
) in Azure DevOps.Select Project settings.
Under Repos, select Repositories.
Select the wiki repository, typically named
<ProjectName>.wiki
.Select the Security tab.
In the security permissions list, find the user or group you want to modify, or select a group like Contributors to modify permissions for all members of that group.
To add a new user, modify permissions for existing groups that the user is already a member of.
Note
The exact method for adding users and groups might vary. If there isn't an option to add users directly in the repository security settings, you might need to add users to existing project groups, like Contributors, through Project settings > General > Teams or Project settings > Permissions.
To grant Edit permissions, locate the Contribute permission and set it to Allow.
The changes save automatically.
Other considerations
When you assign permissions to project users, review the following considerations:
Ensure the user or group has the necessary access level to the Azure DevOps project.
Review and adjust other permissions as needed to maintain security and proper access control, such as Read, Delete, and Manage.
Stakeholder wiki access
Users with project Stakeholder access have permissions set for private and public projects.
Private projects
Users with Stakeholder access in a private project can read provisioned wiki pages and view revisions, but they can't edit them. For example, Stakeholders can't create, edit, reorder, or revert changes to project wiki pages. These permissions can't be changed.
Stakeholders have no access to read or edit published code wiki pages in private projects. For more information, see the Stakeholder access quick reference for project and code wikis.
Public projects
Stakeholders have full access to wikis in public projects.
For more information about Stakeholder access, see About access levels, Stakeholder access, Public versus private feature access.
Note
You can set permissions for the entire wiki, but not for individual pages.