Manage Wiki permissions

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018

Learn about managing permissions for your wiki. By default, all members of the Contributors group can edit Wiki pages.

Manage wiki permissions

By default, all project contributors have read and edit access of the wiki repository. You can grant or restrict access to who can read and edit wiki pages by managing the wiki repository permissions. For more information about permissions in Azure DevOps, see Get started with permissions, access, and security groups.


Feature availability: The built-in wiki is available with TFS 2018 and later versions.

To open the Security dialog, choose More actions > Wiki security.

Wiki, Choose More, select security

For definitions of each repository permission, see Git repository permissions.

Wiki security dialog/

Don't have access to create a page?

If you don't have access to create a wiki page, you need to contact an administrator to grant you adequate permission on the underlying Git repository of the wiki.

Stakeholder wiki access

Private projects

Users with Stakeholder access in a private project can read provisioned wiki pages and view revisions, however they can't do any edit operations. For example, Stakeholders can't create, edit, reorder, or revert changes to project wiki pages. These permissions can't be changed.

Stakeholders have zero 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.


Q: Is it possible to grant permissions on a per-page basis?

A: No, permissions to access the wiki are made for all pages and not individual pages.