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.

#Create a regular sub-account

The account owner can create a member under Sub-accounts with a sign-in email, initial password, display name, and role. The sign-in email cannot be changed after creation. To correct an email, create the right account and disable or remove the old one.

The management actions have different effects:

• Change role: change which business sections the member can access.
• Reset password: keep the account and role while replacing its password.
• Disable: temporarily block sign-in for leave, handoff, or a security review.
• Delete: permanently remove the sub-account; this cannot be undone.

#Maintain permission sets with roles

A role is a named set of visible sections. A custom role can include Chat, Shop Management, Shop Analytics, Customer Service, Affiliate, Ads, Inventory, Billing, and other available scopes. Changing a role updates every sub-account that uses it. Move all members to another role before deleting a custom role.

Built-in roles such as Business Developer, Business Developer Supervisor, and Customer Service cannot be edited or deleted. Create a custom role when the team needs a different combination of sections.

#Manage BD logins from Team & Channels

An individual BD login is not created through the regular New sub-account form. Create it under Affiliate → Team & Channels → Team operations → BD detail → Login account. The system binds it to that BD and grants the fixed BD workspace.

The login appears in the Sub-accounts list, but it cannot be edited, disabled, or deleted from Account. Return to Team & Channels to reset its password, disable, enable, or remove it. This keeps the identity tied to exactly one BD and that BD's Creator ownership.

A BD login sees its own Creator work and analytics details, while an Affiliate supervisor can see the whole team and manage Campaigns, Team & Channels, policy, and global analytics. Creating the login does not change AI assisted / Human only mode or reassign any Creator.

#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. For a BD login, confirm that the change belongs in Team & Channels rather than the regular sub-account form.
3. Check which Chats, Scheduled Tasks, or business services depend on it.
4. Create and validate the replacement before changing a production default.
5. 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.