Account, Members & Runtime Permissions

#Account centralizes members and Agent permission boundaries

Open Account to see the signed-in identity, subscription, and quota. Account owners can also manage member accounts here. Assign scopes according to the person’s real responsibility. A hidden sidebar item is not a backend security boundary, so permission assignment should follow least privilege.

APP CAPTUREThe English light-theme Account page with profile, members, tool surfaces, and run profiles.

#Members and roles

Scopes can separate Shop Management, Shop Analytics, Customer Service, Affiliate, Ads, Inventory, Billing, and other responsibilities. Give each member only the modules required for their role. Update or remove access promptly when responsibilities change; do not rely on an informal team convention.

#Tool Surfaces and Run Profiles

The Account page also manages two layers of Agent capability:

• Tool Surface: defines a reusable set of available tools.
• Run Profile: selects concrete tools or a Tool Surface and may become the account default.

Chat and Scheduled Tasks can use Run Profiles. Grant tools by task instead of placing every tool in one universal profile. Customer Service and Affiliate may also select service-specific models or profiles in Shop settings; see Models, Devices & Runtime.

#Before changing a configuration

1. Identify whether the change concerns member scope, a Tool Surface, or a Run Profile.
2. Check which Chats, Scheduled Tasks, or business services depend on it.
3. Create and validate the replacement before changing a production default.
4. Confirm there are no dependencies before deletion, and retain at least one viable execution path.

Refreshing tools retrieves the current catalogue. It does not decide which tools are appropriate for the business; that remains an account administrator decision.