Set each teammate’s access by integration, then decide which changes can proceed and which need a person’s review. AI workflows work within the access and controls configured for your account.
Choose read only, read and write, or neither for each teammate on each integration. Owner, finance, merchandising, ops, and analyst are example roles; access can be set around your team. AI workflows use only the information available under those permissions.
| Role | Sees | Can do | Never sees |
|---|---|---|---|
| Owner / Admin | Everything | Everything | · |
| Finance | Revenue, margins, payouts, fees | Reconcile, export, bands | Listing controls |
| Merchandising | Sales by marketplace, catalog, cover | Listings, price, campaign, and homepage drafts, queued | Margins, payout accounts |
| Ops | Orders, inventory, shipping | Reorders, purchase orders queued, stock sync within the cap | Margins, pricing bands |
| Analyst | Trends across marketplaces, PII-stripped | Read only | Costs, identities, credentials |
Set and revisit access as your team changes. Marketplace credentials are stored separately from company data.
Where a connected workflow captures the previous value, your team can refer to it when reviewing a change. Recovery options depend on the system and action.
Where available, configure price bands or stock caps as workflow rules—not merely as guidance in an AI prompt.
Set approval steps for supported actions so the right person can review proposed work before it proceeds.
Who asked, which marketplace, when, and why. You can look that up later.
Use connected business data to see what changed and assess its effect. The information available depends on the integration and workflow.
Orders, catalog, inventory, and payout information for a brand are kept in that brand’s database. Data is not mixed with another brand’s data or used to train models.
Access to a brand’s company data is limited to people assigned to that account. Your team’s integration permissions are set separately, so each person sees only the connections their role requires.
One brand’s orders are not included in another brand’s data. Your company data can be exported.
Marketplace passwords are not stored in the company data database.
Work on a brand is limited to the people assigned to that account. It is not a shared login for the company.
These are examples of workflow settings. Available actions and defaults depend on the connected system, account permissions, and agreed scope.
| Action type | Default behavior | You can change it to |
|---|---|---|
| Read / answer a question | Available to authorized users | · |
| Inventory change within a configured cap | Set per workflow | Require approval |
| Price change within a configured band | Set per workflow | Require approval |
| Listing publish | Choose review steps | Require approval |
| Campaign, email, or homepage change | Choose review steps | Require approval |
| Purchase order | Choose review steps | Require approval |
| Change outside a configured limit | Hold for review or block | Review the configured limit |
Illustrative example: a requested Faire price change exceeds the configured limit. Depending on the workflow, it can be held for a person to review rather than proceeding automatically.
A teammate asks to change a Faire price. This scenario illustrates how a configured rule can apply to an AI-assisted workflow.
If the requested change exceeds a configured threshold, the workflow can stop for review when that control is supported and enabled.
The appropriate next step depends on the connected system and the rules the company has configured.
Review change history, including the person, connected system, and workflow status where those details are available. Configure approval steps around the actions and controls supported by your integrations.
The person who sent the instruction. When the approval queue holds a listing for a human yes, that line still names who asked.
Where a workflow captures the value before a change, it can help your team review what happened. Recovery options depend on the connected system and action.
Faire on the held raise. Each line names its own channel, the same way a listing publish names the marketplace waiting on your click.
Review the workflow status to see whether a change proceeded, needs approval, or stopped at a configured limit.
We’ll discuss which people need access to which integrations and where a person should review an AI-assisted action.
Free assessment →