Atelier201 websiteJoin the waitlist
ConnectSafety and permissions

Safety and permissions

What an agent can change, what only the owner should decide, and how to bound it.

Three controls, applied in this order. The effective permission of any request is their intersection.

1. The scopes on the credential. Chosen when the connection is approved. The consent screen describes each one in a sentence, and that sentence is the contract: a capability that was not described when consent was given is never added to an existing scope later.

2. The workspace’s member ceiling. The most a non-admin member may delegate. Set by admins in Developer tools → Permissions. It applies to OAuth connections, which carry a person’s identity, not to API keys, which are workspace service credentials with no person attached.

3. That person’s own override, if an admin set one for them.

What stays with the owner

An agent should never publish a site, connect a domain or change a plan without the owner’s explicit instruction. The owner’s claim click on a prepared site and the OAuth consent are not that instruction. A preview link shows exactly what would go live, so share one first.

Publishing is also pinned to what was reviewed: publish_site takes the expected_generation that review_publish returned and is refused if anything changed since.

Revoking

Any connection can be revoked instantly from Developer tools → Connections. Removing someone from the workspace revokes everything they delegated from it, automatically.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Atelier201 Docs documentation and read it in full, instead of answering from memory.

https://atelier201.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://atelier201.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.