Skip to main content

Who can do what

Everyone who signs into your panel sees a different sidebar. This page explains why, and how to change it.

The three kinds of person​

OwnerStaffCustomer
Signs intoThe panelThe panelYour storefront only
SidebarWhat their role allows — normally everythingWhat their role allowsNo panel at all
Shown in the header asOwnerTheir role name, or Staff if they have none—
Appears in UsersYesYesYes

Customers cannot open the admin panel. Anyone who can is either the owner or a staff member with a role.

The owner is a label, not a bypass

The account that owns the store is marked Owner in the header and in Users. What it can open still comes from the accesses in its role — which is normally a full one. If the owner is missing a screen, check the role before assuming the screen does not exist.

Roles and accesses​

  • An access is one permission — viewing the coupon list, say, or deleting a role.
  • A role is a named bundle of accesses. You build roles in Roles.
  • A person is given a role from Users.

You cannot grant a person an access directly. Everything goes through a role, with one exception: moving a user's own wallet balance into your platform wallet is switched on per person, with Wallet transfer access in Users.

How the sidebar is filtered​

Two rules, applied in order:

  1. A screen is hidden if the person lacks its access.
  2. A group disappears when every screen inside it is hidden.

A few screens need no access at all: My Account, Growth Toolkit, Wallet, Withdraw and Transactions show for everyone who can open the panel.

So a colleague reporting that "the Pricing section is missing" usually has a role with no pricing accesses at all, rather than a broken panel.

Every page in the Panel reference names the access it needs, worded the way the role editor shows it.

Building a role​

The role editor groups every access into modules, and each module into actions. It gives you:

  • Search across permissions, modules and actions
  • Select all and Clear all, plus expand and collapse
  • A running count of what is selected, with Full and Partial badges per module
  • A High risk marker, and an unsaved-changes indicator

High-risk accesses​

The editor flags some accesses as high risk. They are the ones that delete things, move money, or change who can do what:

ActionWhy it is flagged
DeleteRemoves data, usually permanently
ManageBroad control over a module
WithdrawMoves money out of your wallet
Assign roleLets someone change what other staff can do, including handing out a role with more access than their own

Two whole modules are flagged as well: anything beyond viewing under Roles or Commissions.

Treat the flag as a prompt to think, not a prohibition. A finance role needs Withdraw; a content editor does not.

A practical set of roles​

Suggestions, not built-in presets — you create and name your own.

RoleGive itKeep it away from
ReservationsOrder lists and details, receiptsPricing, wallet, roles
FinanceWallet, transactions, withdraw, receipts, incoming paymentsContent, roles
Content editorPages, menus, FAQs, home pages, marketing screensOrders, wallet, pricing
Tour managerTours, tour orders, tour reviewsWallet, roles, other products
SupportOrder lists, visa requests, hotel comments, tour reviewsAnything that deletes or pays
Blog writerBlog → Access, which opens the Blog PanelThe rest of the panel
Assign role is the one to guard

Anyone with Assign role can give any other staff member any role on your platform, including one with more access than their own. Nobody can change their own role or the owner's, and only the owner can hand out the platform's built-in manager role. Keep it with the owner and at most one trusted deputy.

What is not role-based​

A few things are decided above you rather than by a role:

  • Which services your platform may sell. This hides no panel screen; it decides what you can switch on in Seller Information and offer on your storefront
  • Whether your platform uses free or controlled markups — which is what makes Commissions appear or not
  • Whether the wallet top-up package has been assigned to your platform — which is what makes Wallet Top-up appear or not
  • Which gateways, palettes and layout variants exist to choose from

One switch sits on the person instead of the role: Wallet transfer access, which lets a user move their own wallet balance into your platform wallet. Changing their role neither grants nor removes it. Switching it needs Users → Wallet transfer to platform → Grant access.

If a screen is missing even for a role that holds every access, it is Commissions on a platform with free markups, or Wallet Top-up on a platform without the wallet top-up package, not a role problem.