{"ArticleId":null,"Name":"Store owner panel overview","Content":"\n\u003Cp\u003EGrandNode can run many stores from one installation: each store has its own domain, catalog visibility, currencies, languages, settings, payment and shipping configuration. The \u003Cstrong\u003EAdmin panel\u003C/strong\u003E at \u003Ccode\u003E/admin\u003C/code\u003E manages all of them at once. The \u003Cstrong\u003Estore owner panel\u003C/strong\u003E at \u003Ccode\u003E/store\u003C/code\u003E is a second back office built for the person who runs just one of those stores. A store manager logs in, sees the data of their own store only, and can change it without being able to touch any other store or any system-wide configuration.\u003C/p\u003E\n\u003Cp\u003EUse the store owner panel when you operate several stores (brands, countries, franchisees, partner shops) and want each one run by its own team, while the platform owner keeps the Admin panel for global work: installing plugins, creating stores, managing permissions and system settings.\u003C/p\u003E\n\n\u003Ch2 id=\u0022who-it-is-for\u0022\u003EWho it is for\u003C/h2\u003E\n\u003Cul\u003E\n\u003Cli\u003E\u003Cstrong\u003EThe store manager\u003C/strong\u003E \u2014 a customer account that belongs to the \u003Cstrong\u003EStore manager\u003C/strong\u003E customer group and has a store selected in the \u003Cstrong\u003EManager of store\u003C/strong\u003E field. This person uses \u003Ccode\u003E/store\u003C/code\u003E every day: products, orders, customers, promotions and the store\u0027s own settings.\u003C/li\u003E\n\u003Cli\u003E\u003Cstrong\u003EThe administrator\u003C/strong\u003E \u2014 creates the store, creates or promotes the manager account, and decides through \u003Cstrong\u003EConfiguration \u2192 Permissions\u003C/strong\u003E which parts of the panel the Store manager group can open. See \u003Ca href=\u0022/store-panel-access\u0022\u003EGive someone access to the store owner panel\u003C/a\u003E.\u003C/li\u003E\n\u003C/ul\u003E\n\n\u003Ch2 id=\u0022how-it-differs-from-admin\u0022\u003EHow it differs from the Admin panel\u003C/h2\u003E\n\u003Cp\u003EThe two panels share most of their screens \u2014 the store owner panel reuses the same product, order, customer and settings editors \u2014 but every screen is filtered through the manager\u0027s store. The differences that matter in practice:\u003C/p\u003E\n\u003Ctable\u003E\n\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EArea\u003C/th\u003E\u003Cth\u003EAdmin panel (\u003Ccode\u003E/admin\u003C/code\u003E)\u003C/th\u003E\u003Cth\u003EStore owner panel (\u003Ccode\u003E/store\u003C/code\u003E)\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\n\u003Ctbody\u003E\n\u003Ctr\u003E\u003Ctd\u003EScope\u003C/td\u003E\u003Ctd\u003EAll stores; a store selector on lists and settings.\u003C/td\u003E\u003Ctd\u003EOne store, fixed. No store picker; new records are assigned to the manager\u0027s store automatically.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003EProducts, categories, brands, collections\u003C/td\u003E\u003Ctd\u003EEverything, including items shared by several stores.\u003C/td\u003E\u003Ctd\u003ECreates items limited to its own store. Items that are global or shared with other stores are visible but open read-only.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003EOrders, shipments, merchandise returns, payment transactions\u003C/td\u003E\u003Ctd\u003EAll orders.\u003C/td\u003E\u003Ctd\u003EOnly orders placed in its own store.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003ECustomers\u003C/td\u003E\u003Ctd\u003EAll customers, groups, tags, vendors, sales employees.\u003C/td\u003E\u003Ctd\u003EOnly registered customers of its own store, and only when per-store customer accounts are enabled.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003ESettings\u003C/td\u003E\u003Ctd\u003EGlobal values (\u0022All stores\u0022) or per-store overrides.\u003C/td\u003E\u003Ctd\u003EAlways saves the store\u0027s own override. Some system-wide fields are not shown or cannot be changed.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003EPayment, shipping, tax\u003C/td\u003E\u003Ctd\u003EGlobal and per-store.\u003C/td\u003E\u003Ctd\u003EActivates methods and edits restrictions and settings for its own store only.\u003C/td\u003E\u003C/tr\u003E\n\u003Ctr\u003E\u003Ctd\u003ESystem\u003C/td\u003E\u003Ctd\u003EPlugins, stores, permissions, ACL, logs, maintenance, import/export.\u003C/td\u003E\u003Ctd\u003ENot available.\u003C/td\u003E\u003C/tr\u003E\n\u003C/tbody\u003E\n\u003C/table\u003E\n\u003Cp\u003EA store manager has no access to \u003Ccode\u003E/admin\u003C/code\u003E at all. The Admin panel turns away any account that is in the Store manager group or has a store in \u003Cstrong\u003EManager of store\u003C/strong\u003E, even if the Access Admin Panel permission were granted, so a manager cannot step outside their store by that route.\u003C/p\u003E\n\n\u003Ch2 id=\u0022what-a-store-manager-sees\u0022\u003EWhat a store manager sees\u003C/h2\u003E\n\u003Cp\u003EAfter signing in at \u003Ccode\u003E/store/login\u003C/code\u003E (or from the \u003Cstrong\u003EStore portal\u003C/strong\u003E button in the storefront account menu), the manager lands on the dashboard. The header shows the store name next to a store icon, so it is always clear which store is being managed. The left menu is the same as in the Admin panel, minus everything the manager is not allowed to use.\u003C/p\u003E\n\u003Cfigure\u003E\u003Cimg src=\u0022/Plugins/Theme.GrandNodeCom/Content/kb/store-panel/dashboard.webp\u0022 alt=\u0022Store owner panel dashboard for the store GrandNode Demo with online visitors, active carts, today\u0027s orders and charts\u0022 width=\u00221440\u0022 height=\u0022900\u0022 loading=\u0022lazy\u0022\u003E\u003Cfigcaption\u003EThe store owner panel dashboard. The store name in the header and under the page title shows which store the manager works in.\u003C/figcaption\u003E\u003C/figure\u003E\n\u003Cp\u003EThe menu groups are \u003Cstrong\u003EDashboard\u003C/strong\u003E, \u003Cstrong\u003ECatalog\u003C/strong\u003E, \u003Cstrong\u003ESales\u003C/strong\u003E, \u003Cstrong\u003ECustomers\u003C/strong\u003E, \u003Cstrong\u003EMarketing\u003C/strong\u003E, \u003Cstrong\u003EContent\u003C/strong\u003E, \u003Cstrong\u003EReports\u003C/strong\u003E, \u003Cstrong\u003EConfiguration\u003C/strong\u003E and \u003Cstrong\u003ESettings\u003C/strong\u003E. Which entries appear depends on the permissions of the Store manager group; a fresh installation grants only a basic set (catalog, orders, shipments, merchandise returns, payment transactions, customers, reports), and the administrator adds the rest. The \u003Ca href=\u0022/store-panel-dashboard-and-navigation\u0022\u003Edashboard and navigation\u003C/a\u003E article walks through every menu entry.\u003C/p\u003E\n\n\u003Ch2 id=\u0022how-scope-is-decided\u0022\u003EHow the store scope is decided\u003C/h2\u003E\n\u003Cp\u003EThe panel does not ask which store you want: the store is taken from the \u003Cstrong\u003EManager of store\u003C/strong\u003E field of the signed-in customer. Every list is filtered by it, every new record is stamped with it, and every save is checked against it on the server. Changing the value in the request, or opening a URL of another store\u0027s order or product, simply sends you back to the list. That is what makes it safe to hand a store to an external partner.\u003C/p\u003E\n\u003Cp\u003EFor catalog items and several configuration objects GrandNode uses one rule throughout: the manager may \u003Cem\u003Eedit\u003C/em\u003E an item only when it is limited to exactly one store \u2014 theirs. An item that is visible in all stores, or shared by several, belongs to the administrator; the manager can open it to look, copy it, and use it in their own store, but not change or delete it. A yellow warning at the top of the editor says so.\u003C/p\u003E\n\n\u003Ch2 id=\u0022related\u0022\u003ERelated\u003C/h2\u003E\n\u003Cul\u003E\n\u003Cli\u003E\u003Ca href=\u0022/store-panel-access\u0022\u003EGive someone access to the store owner panel\u003C/a\u003E\u003C/li\u003E\n\u003Cli\u003E\u003Ca href=\u0022/store-panel-dashboard-and-navigation\u0022\u003EDashboard and navigation\u003C/a\u003E\u003C/li\u003E\n\u003Cli\u003E\u003Ca href=\u0022/docs-customers\u0022\u003ECustomers\u003C/a\u003E \u2014 customer groups and customer accounts in the Admin panel\u003C/li\u003E\n\u003C/ul\u003E\n","ParentCategoryId":"6abdec6d83d2816248229f43","SeName":"store-panel-overview","MetaKeywords":null,"MetaDescription":"What the GrandNode store owner panel at /store is, who uses it, and how it differs from the Admin panel in a multi-store installation.","MetaTitle":null,"AllowComments":false,"Captcha":{"ReCaptchaChallengeField":null,"ReCaptchaResponseField":null,"ReCaptchaResponseValue":null,"ReCaptchaResponse":null},"RelatedArticles":[],"CategoryBreadcrumb":[{"Name":"Store owner panel","Description":null,"IsCurrent":false,"Children":null,"Parent":null,"SeName":"docs-store-panel","Id":"6abdec6d83d2816248229f43","UserFields":[]}],"AddNewComment":{"CommentText":null,"DisplayCaptcha":false,"Id":null,"UserFields":[]},"Comments":[],"Id":"6abdec6d83d2816248229f45","UserFields":[]}