Can an agency add a client’s store without the client knowing?
No. Either somebody at the store’s own domain approves it by email, or a record is published in a DNS zone the agency does not control. Both are the store saying yes.
A workspace shares stores between people. This page lists what an owner, an admin and a follower can each do, how invitations work, how a client’s store is added with its owner’s approval, and the second factors an account can use.
Everything an admin can, plus making somebody else an owner and changing or removing another owner. A workspace always keeps at least one owner: the last one cannot be removed or demoted.
Invites and removes people, adds and removes client stores, and starts or cancels subscriptions. Cannot change an owner.
Reads every report the workspace can read and receives its alerts and digests. Changes nothing and spends nothing.
A store joins a workspace only when whoever runs it agrees. There are two ways to show that.
You name an address at the store’s own domain. We email that person a link, and the store joins the workspace when they approve it. Nothing you send can approve it for them.
We give you a TXT record to publish on the store’s domain, and you check it once it has propagated. A store on a shared platform domain has no zone of its own, so it has to be added by its own domain or by email.
A request that is not approved or verified expires after 14 days.
No. Either somebody at the store’s own domain approves it by email, or a record is published in a DNS zone the agency does not control. Both are the store saying yes.
Nothing. Subscriptions are per storefront, not per person, and a follower cannot start one.
Their access ends at once, including the reports and the alerts. Membership is checked on every request rather than copied when they joined.
For agencies running a book of client stores, see Ottom for agencies. Who receives each alert is on the alerts page.