Account Panel, Store App, Modules and Menus Explained

Level Basic Role Owner, Admin Module Account Panel and Store App About 7 minutes
Updated

The Account Panel and Store App work together, but they are not the same place. Understanding the boundary early prevents two common mistakes: looking for a setting in the wrong area and treating every missing menu as an application error.

The short version: the Account Panel manages the shop application; the Store App runs the shop. Modules provide functions; access rights limit who may use them.

Before you start

  • The Store App has been created and can be opened.

Steps

  1. Separate the Account Panel from the Store App

    The Account Panel manages Store App ownership, access addresses, plans, vouchers, and Module Setting. The Store App is where shop operations run: shop settings, master data, repairs, stock, transactions, and available reports.

    Account Panel

    The Account Panel showing one Store App with its domain plan voucher Upgrade and Module Setting controls
    The Account Panel manages the shop application; the domain on this card opens the Store App for daily operations.

    Store App

    The Store App showing its operational menu and repair list with statuses technicians billing and actions
    The Store App is where the team runs repairs, transactions, inventory, and other daily work.
  2. Understand that menus follow modules

    Modules add specific groups of functions to the Store App. If a function is unavailable, first check whether its module is installed and active before changing unrelated settings.

  3. Separate modules from access rights

    Modules determine which functions are available to the Store App. Access rights determine which of those functions a staff account may see or use. A menu can be hidden by either layer.

  4. Do not install every module just to begin

    Start with what the first repair workflow needs. Optional modules can be chosen later from the module catalog; installation, removal, and token activation belong in the Manage Modules guide.

  5. Continue with the right data order

    After understanding each area, learn the difference between master and transaction data. That concept determines what must be prepared before recording the first repair.

What you end up with

You know where Store Apps are managed, understand the two main reasons a menu can be hidden, and can continue setup without installing modules at random.

If something goes wrong

A required menu is missing

Check the related module in the Account Panel, then check the access rights of the account currently used in the Store App.

Not sure whether a setting belongs in the Account Panel or Store App

Plans, vouchers, access addresses, and modules belong in the Account Panel; shop settings and daily work belong in the Store App.

I have two shops — why is the data not combined

It is not meant to be. Each Store App stands alone with its own data. The Account Panel is where you switch between shops, not where their contents merge.

The module is installed but the menu still is not there

Two separate things decide whether a menu appears: the module being installed, and your user access allowing it. The module opens the door; access rights decide who walks through. Check both, not one.