# Zuwiki

## Access Grants

> Category: Access & Sharing

---

## Pages

- [Welcome to Zuwiki](https://docs.zuwiki.com/welcome-to-zuwiki)

### Getting Started

- [Create Your First Wiki](https://docs.zuwiki.com/getting-started/create-your-first-wiki)
- [Organize with Categories](https://docs.zuwiki.com/getting-started/organize-with-categories)
- [Publish Your First Page](https://docs.zuwiki.com/getting-started/publish-your-first-page)

### Core Concepts

- [Wikis, Categories, and Pages](https://docs.zuwiki.com/core-concepts/wikis-categories-and-pages)
- [Page Lifecycle](https://docs.zuwiki.com/core-concepts/page-lifecycle)
- [Page History and Restore](https://docs.zuwiki.com/core-concepts/page-history-and-restore)

### Access & Sharing

- [Public vs Internal Wikis](https://docs.zuwiki.com/access-sharing/public-vs-internal-wikis)
- [Visibility for Public Wikis](https://docs.zuwiki.com/access-sharing/visibility-and-access)
- [Share Links](https://docs.zuwiki.com/access-sharing/share-links)
- [Access Grants](https://docs.zuwiki.com/access-sharing/access-grants)
- [Classification and Sensitivity](https://docs.zuwiki.com/access-sharing/classification-and-sensitivity)

### Editor Guide

- [Markdown Basics](https://docs.zuwiki.com/editor-guide/markdown-basics)
- [Linking Between Pages](https://docs.zuwiki.com/editor-guide/linking-between-pages)
- [Icons and Visual Touches](https://docs.zuwiki.com/editor-guide/icons-and-visual-touches)
- [Rich Content Blocks](https://docs.zuwiki.com/editor-guide/rich-content-blocks)
- [OpenAPI Pages](https://docs.zuwiki.com/editor-guide/openapi-pages)

### Plans & Account

- [Plans and Limits](https://docs.zuwiki.com/plans-account/plans-and-limits)
- [Custom Domain](https://docs.zuwiki.com/plans-account/custom-domain)
- [Zuwiki for Open Source](https://docs.zuwiki.com/plans-account/zuwiki-for-open-source)

### Integrations

- [MCP Server](https://docs.zuwiki.com/integrations/mcp-server)

---

# Access Grants

Access grants control who can read and edit an **internal knowledge wiki**. They are the equivalent of visibility for the internal world: instead of a public setting, access is expressed as roles given to teams and people. For the public side, see [Visibility for Public Wikis](/access-sharing/visibility-and-access), and for the difference between the two worlds see [Public vs Internal Wikis](/access-sharing/public-vs-internal-wikis).

You manage all of this in the wiki settings under **Security**, in the **Members & access** area.

## Read access: the Restrict access toggle

Internal wikis default to open inside your organization. The **Restrict access** toggle decides whether that holds:

- **Off** (the default): every organization member can read the wiki. You still add grants below, but only to hand out editing rights.
- **On**: only the teams and people listed below can read the wiki. Everyone else in the organization loses access.

Organization owners and administrators always have full access and never need to be listed.

## Roles

Each grant pairs a principal with a role. Roles form a ladder, and each one includes everything below it:

- **Viewer**: read the content.
- **Commenter**: read, plus take part in discussion on the content.
- **Editor**: read and write, create and edit pages.
- **Maintainer**: full control of the resource, including its structure, settings, and who else has access.

## Who you grant to

A grant can target one of three kinds of principal:

- **All organization members**: a baseline role for everyone in the org. Useful to give the whole company Viewer on a restricted wiki, or Editor on an open one.
- **A team**: everyone on a managed team. Teams are created and maintained under your organization settings, so access follows team membership automatically as people join and leave.
- **A single person**: one named member of the organization.

## How grants combine across the tree

Grants can apply to a whole wiki, or to a single category or page. Access is resolved along the hierarchy from the page up through its parent pages and category to the wiki, and the **highest** role on that path wins.

In practice this means:

- A role granted on the wiki covers everything inside it.
- A more specific grant on a category or page can raise someone's role for just that part of the tree.
- You cannot use a child grant to take access away that was given higher up. To lock a wiki down, turn on Restrict access and grant deliberately.

## A few rules of thumb

- Lead with **teams** over individuals. A team grant stays correct as people come and go.
- Keep **Restrict access off** unless the content genuinely needs to be narrower than the whole organization. Most internal knowledge benefits from being readable.
- Use **Maintainer** sparingly. Editors can write all day without being able to change who gets in.