What an assistant can read and change

Documentation / Agentic editing and connections

An assistant uses the permissions of its Beeboo connection. It does not become a super administrator simply because it can see a tool. Your account must have access to the selected website, and the connection must include the scope required by the operation.

Read before changing

With read access, an assistant can list accessible websites, inspect pages and their metadata, read navigation roots and translations, inspect templates, and retrieve site settings. Page revision tools can list history and read complete snapshots. Shared-shell tools expose the source, draft, active revision, and review context.

Ask the assistant to identify the website domain, page ID, content language, and current revision before proposing an edit. A suitable first request is: “List the websites I can manage. Do not change anything.”

Approve a bounded change

Write access enables supported content mutations, including page creation, updates, deletion, navigation changes, templates, and selected site settings. Legal generation and shared-shell changes have their own tools. Website creation and changes to whole-site visibility require the current super-admin role as well as write scope.

Ordinary update_page and update_page_by_path calls change the saved page immediately. They do not operate on editor cloud drafts. Ask for a content proposal first, then approve the exact page and fields. Include the latest page version to detect intervening edits.

Verify the result

Have the assistant read back the saved page and inspect the rendered route. Check navigation, links, language, and availability yourself. A tool error can follow partial changes in multi-file operations, so inspect reported results before retrying. Use saving and recovery when a revision needs review.