--- title: "Where does your restaurant AI assistant's access stop?" date: 2026-10-14 updated: 2026-10-14 lang: en tags: ["guides", "operations", "software"] summary: "Read access can reveal business information, while a writing tool can publish immediately. Review both before approving a connection." canonical: https://rosuii.com/blog/restaurant-ai-safety-permissions author: "Rosuii Team" --- # Where does your restaurant AI assistant's access stop? Read access can reveal business information, while a writing tool can publish immediately. Review both before approving a connection. **Last verified: 2026-10-14** Rosuii's restaurant connector cannot take, void or refund payments. It has no tools for changing prices, creating staff logins, changing permissions or plans, or reading or editing inventory. With permission, it can read orders and sales and immediately publish menu or website content. Approving a new connection requires a restaurant admin account or `settings.edit` permission. Reading reports later is a separate `reports.view` permission check. Having no payment tool does not make every action inconsequential. An incorrect description can mislead a guest; report access can reveal private figures. Read the [connection permission list](https://rosuii.com/ai-assistant) by task. ## Separate four kinds of access | Task | Permission | Meaning | | --- | --- | --- | | Read sales and dish rankings | `reports.view` | Reading report data, not executing payments | | Read orders or the staff list | `orders.view` or `employees.view` | A separate permission for each list | | Edit descriptions or branch item availability | `menu-items.edit` | Immediate public menu changes | | Edit public profile fields or FAQs | `settings.edit` | Immediate website changes | Reading menus needs `menu-items.view`; reading the public profile needs `settings.view`. One permission does not grant the others. The account receives its permitted subset of twelve connector tools. ## Branch access and restaurant-level content An assigned branch limits orders, sales, staff and per-branch dish availability; a branch the person is not assigned to is refused. Menu descriptions, the public profile and the website FAQ are restaurant-level and are not divided by branch. Editing descriptions and switching branch item availability share `menu-items.edit`, but their scope differs. The branch list is limited to an assigned branch, and availability changes refuse another branch. A description edit changes the restaurant-level menu. ## Requesting a draft is different from an enforced approval gate Try: “এই খাবারের বর্ণনার খসড়া দেখাও। আইডি ও আগের লেখাও দেখাও। আমি বলার আগে সংরক্ষণ কোরো না।” It asks for the draft, item ID and previous wording before any save. Check the facts, then give a specific save instruction. The assistant controls that conversation. Rosuii's writing tools do not enforce a separate draft-approval stage. A save changes the public website immediately. Understand that distinction before enabling writing access. ## Permission changes affect new requests Each request rechecks the approving account's active status and permissions. Deactivating that account stops new connector requests. Removing report access also removes access to the corresponding tools. This is not a promise to erase information already delivered into a chat. The assistant provider controls its conversation-retention rules. Stopping new access and deleting an earlier copy are different actions. ## Run a small permission check - Connect your own account and keep passwords out of chat. - Start with reading tasks and compare the tool list with your permissions. - Asking for staff names and account types needs employee-list access; it is not a salary or attendance report. - Use a controlled test account to check deactivation without disrupting a real employee. - If testing a public edit, use approved sample wording and inspect the saved result. The public MCP service explains Rosuii the product and contains no private restaurant data. Read the [two-service distinction](https://rosuii.com/features/ai-discoverability) and Rosuii's [published security information](https://rosuii.com/security) before deciding how your team should connect. ## How we calculated and verified this Rosuii publishes this guide about its own connector. We reviewed the tool definitions, permission checks and published product information on 14 October 2026. This is an implementation and content review, not a new production account test. Example questions are instructions to try, not recorded customer results. ## Related guides - [Public product information and restaurant account access](https://rosuii.com/features/ai-discoverability) - [Check Rosuii plans and conditions](https://rosuii.com/pricing) **See this workflow in Rosuii:** [See the restaurant connector and its permissions](https://rosuii.com/ai-assistant) ## Sources checked - [Rosuii restaurant connector: tools, permissions and limits](https://rosuii.com/ai-assistant) - [Rosuii public AI information and account connector](https://rosuii.com/features/ai-discoverability) [Start using Rosuii for free](https://rosuii.com/register) ## Related guides - [Connect an AI assistant](https://rosuii.com/ai-assistant) - [Restaurant POS](https://rosuii.com/features/restaurant-pos) ## FAQ ### Does the staff list include salary and attendance? No. It returns roster fields such as names, account types, branches and active status. It has no salary or attendance-reading tool. ### Does removing access delete old chats? No. Blocking new requests does not demonstrate deletion of earlier conversations. Review the assistant provider's retention controls separately. ### Is description editing a narrower permission than availability editing? Both use menu-items.edit in the connector. Understand both actions before granting that permission for only one intended task. --- Canonical: https://rosuii.com/blog/restaurant-ai-safety-permissions Machine-readable site overview: https://rosuii.com/llms.txt