set_guide_access
Preview
This feature is in preview and is subject to change.
Change a Guide'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
{
"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:
Make the MRR definitions guide available to the whole organization
{
"uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"access": "organization"
}
Make a guide private again:
{
"uuid": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
"access": "user"
}
Related
create_guide— Set access at creation time.update_guide_metadata— Change title, description, or topic.- Guides how-to — Step-by-step instructions for creating and managing Guides.