Website Builder
“My colleague can see it and I cannot.” In the Website Builder that sentence usually has one
cause, and it is not a permission: when you sign in, the storefront asks once whether
CP Commerce Admin is installed for your login, and
the screens behind the dashboard tiles take their answer from that for the rest of your session. The
Website Builder is the store manager’s side of a storefront — the dashboard a signed-in person reaches
from the WEBSITE BUILDER button on the Website record in the console, or by adding
/page/website-builder/ to the shop’s own address. The console’s page documents the dashboard and its
tiles; this folder holds the one tile that changes who may use it.
Which page answers your question
| You want to… | Read | Why there |
|---|---|---|
| Let a store manager use the Website Builder | User Permission Manager | Make Admin installs CP Commerce Admin for that login and adds the person to one role. They sign out and back in before anything changes for them |
| Take that access away again | User Permission Manager § Lifecycle, then Tenant Admin | Remove Access takes the role away and leaves the applet, and the applet is what opens the Website Builder. The removal finishes in Tenant Admin |
| Find out why a tile is missing, or hide one | Hiding tiles on the console page | Eleven checkboxes on the Website record, one per tile; two tiles have no checkbox, and a hidden tile is still reachable by its address |
| Change the shop’s menus or page layouts | Menu List and Layout Instance on the console page | The Menu Manager and Layout Manager tiles reach the same records as those two console tabs, so one page describes both doors |
| Change a product’s description, images or price | Doc Item Maintenance | The Product Management tile opens the item master. A store manager who edits a product there edits the record every other channel reads |
| Send a message to everyone who installed your app | Push Notification Configuration | It explains the Firebase credential on the Website record and the settings that decide who is subscribed — what has to be in place before any notification reaches a phone. The storefront’s own Notification tile writes the same record through the same endpoint as the console’s Notification screen, so that page covers both doors (Screens and menus) |
| Run the programmes shoppers book, and choose the day’s highlights | Activities and Facilities and Highlights on the console page | The Activity Manager tile edits the same activity records the console’s Activities screens do, and the Highlight Manager tile is documented under Highlights |
| Know what every other tile does | The dashboard tiles on the console page | Thirteen tiles are defined and two do nothing when clicked; that section names all of them |
What decides whether it opens, and what to settle first
- Admin mode comes from the applet, fetched once per session. Six tiles refuse with Only Admin can access this page until the person holds CP Commerce Admin and has signed in again; the other five open for anyone signed in and answer with that person’s own permissions (whether the Website Builder opens for a person).
- The console’s WEBSITE BUILDER button needs the Website Code to be the storefront’s exact domain (before the button opens anything).
- Decide who may be made admin, and whether the store manager may touch products, before the first promotion — the tile keeps no list and tells nobody (deciding who holds it).
- Hiding a tile is not a permission, and Remove Access does not take the applet away; removal ends in Tenant Admin. A save is live: there is no draft or undo.
After promoting someone, run the two-minute check that the person can work; when something goes wrong, start at User Permission Manager troubleshooting or the console’s Hiding tiles. The console edits the same records through the Website record’s tabs and holds everything that is not a tile — pricing, access restrictions, spending limits, agreements, shipping providers.