# set_guide_access
> Change a Guide's visibility between private and org-wide
Change a [Guide](/key-tasks/guides/)'s visibility to `"user"` (private) or `"organization"` (visible to your whole org). Setting org-wide access is admin-permission gated.

## Description

The `set_guide_access` tool controls who can see and read a guide:

- **`"user"`** — private to the guide's owner. Only you can read or modify it.
- **`"organization"`** — visible to everyone in your MotherDuck organization. Setting this level requires admin permission.

Use this tool to promote a personal guide to org-wide after review, or to make a guide private again. Access is the only visibility mechanism — a guide's topic has no effect on who can see it.

## Input parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `uuid` | string | Yes | The guide's UUID, as returned by `list_guides` or a previous mutation. |
| `access` | string | Yes | `"user"` (private) or `"organization"` (org-wide, admin-permission gated). |

## Output schema

```json
{
  "success": boolean,
  "guide": {
    "id": string,
    "topic": string,
    "title": string,
    "description": string,
    "access": string,       // Updated access level
    "current_version": number,
    "created_at": string,
    "updated_at": string
  },
  "error": string
}
```

## Example usage

**Publish a guide to the whole org:**

```text
Make the MRR definitions guide available to the whole organization
```

```json
{
  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "access": "organization"
}
```

**Make a guide private again:**

```json
{
  "uuid": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "access": "user"
}
```

## Related

- [`create_guide`](../create-guide) — Set access at creation time.
- [`update_guide_metadata`](../update-guide-metadata) — Change title, description, or topic.
- [Guides how-to](/key-tasks/guides/) — Step-by-step instructions for creating and managing Guides.


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fsql-reference%2Fmcp%2Fguides%2Fset-guide-access%2F&page_title=set_guide_access&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.