Understanding Permissions

When you approve a connection you decide what the assistant can read. Grant only what it needs.

Before you start

• An AI tool ready to connect.

Steps

What happens next

• The tool gets an access key bound to this store and exactly those permissions.

Edge cases

• The read permissions. read:store: store profile, staff list and settings. read:orders: order history, line items and status; who bought an order shows only with read:customers too. read:reports: sales reports, transaction summaries and analytics. read:products: the catalog, prices, modifiers, categories, taxes, discounts, charges and your bookable services menu. read:customers: customer profiles and purchase history. read:inventory: stock levels and locations. read:financials: sensitive figures such as cost of goods, gross margin, expenses, tax, cash variance, valuation and profit and loss. read:operations: cashier sessions, events and bookings, and kitchen display pacing. read:staff: per-staff sales, refunds and discount activity, with names, so treat it as personal data.
• The four import permissions are the only way an assistant can write. write:catalog adds products, services, categories, modifier groups, taxes, discounts and charges. write:expenses records expenses, always Pending. write:inventory adds suppliers and draft purchase orders. write:bookings creates appointments and reservations, with no message sent to customers. Each shows a preview and writes only after you approve in the chat. None can delete anything or touch orders, payments or settings.
• A permission not granted is not listed. A call to it is refused as missing. A permission your role no longer allows is refused and drops out of the tool list until it allows it again.
• Who may connect. Store owners and organization admins always can. Everyone else needs AI Connections → Connect on their role. This is separate from the add-on. With Roles & Permissions off, every staff member can connect.
• Who may manage. View sees which assistants are connected. Connect sets one up. Modify manages credentials. Delete revokes. Ticking Connect, Modify or Delete adds View. Personal access tokens stay owner-only, because they are long-lived and work after the person leaves.
• You can grant only what you hold. Two people at one store can see different approval screens, and an owner sees everything.
• An organization connection is read-only and covers every store in the group, comparing sales, stock and transfers. Only the organization's owner or an admin can approve one, and access is re-checked on every request. Per-store work needs a store connection.
• Least privilege. Fewer permissions means less exposure and cleaner audit trails. You can make several connections with different permission sets and revoke them independently.

Works with

Related guides

• AI Connections Overview
• Setting Up AI Access
• Roles and Permissions Overview