Each action on the website needs its own permission, so the person who designs the site does not have to be the person who puts it in front of customers.
The four permissions
| Permission | What it allows |
|---|
| View | Open the Online Store pages |
| Customize | Apply a theme, open the editor, save Preferences, add and remove redirects, restore a version into the draft |
| Publish | Publish from the editor, schedule a publish, go live, set the password page, take the site offline |
| Domains | Connect a domain, Check now, Make main, Remove |
Who holds them
| Role | View | Customize | Publish | Domains |
|---|
| Shop owner | Yes | Yes | Yes | Yes |
| Shop Marketing Manager | Yes | Yes | No | No |
| Other staff roles | No | No | No | No |
The panel has no screen for giving these permissions to another member of staff. Ask support if someone else needs them.
- Shop owner: Shop › Online Store.
- A Shop Manager who has been given the View permission: Online Store in the top bar.
- Shop Marketing Manager: the role holds View and Customize, but its menu has no Online Store link today. Ask support how to reach it.
The header of every Online Store page shows the store status as a chip: Live, Password protected, Draft or Suspended. Below it are the tabs Overview, Themes, Domains, Preferences, Redirects and History. Domains is shown only with the Domains permission.
Designing without publishing
A person with Customize but not Publish can do all the design work. What is different for them:
| Where | What they see |
|---|
| The editor | Publish is greyed out. Its tooltip reads "You do not have permission to publish" |
| The editor, scheduled publish strip | "You do not have permission to publish, so you cannot change the schedule." |
| The editor, Version history | Restore only. Publish, which puts an earlier version live again, is not offered |
| Overview › Store status | "Only someone who can publish may change whether the store is public." |
| Preferences | No Password page card |
Their edits are saved to the same draft. Someone with Publish then opens the editor, reviews the change list and publishes. See Publish.
Permissions are checked again on every save in the editor. If a permission is taken away, an open editor stops saving on its next attempt.