Permissions, suspending a member, and why a button is greyed out

Every member's access is set on their own page, and it is finer than their role.

Roles are presets. Picking one fills in a sensible set of permissions, and changing someone's role resets their access to that role's defaults — the page warns you, because any hand-tuning you did is replaced. "Reset to role" does the same on purpose when you want to start over.

Permissions come in groups — orders, products, customers, delivery, marketing, website, media, team, analytics, settings, and AI — and most split into viewing and managing. The AI group (use the assistant, use AI tools, and a monthly AI credit limit) decides who may spend the store's AI credits. You can toggle a whole group at once or set individual ones. A member with view but not manage sees the section read-only: the controls are visibly disabled rather than failing when pressed, which is why a button can look greyed out for one person and work for another. That is almost always the answer when someone says a button "does nothing".

Orders are set page by page. The Orders group has one row for each order page — Orders, Abandoned, On delivery and Archive — and each row has four settings:

  • Off — they cannot open that page at all.
  • View only — they see every order on that page as a list, but cannot open an order, change it, or be given one. They never appear in assign lists or distribution rules for that page.
  • Theirs — they see and work only the orders that belong to them.
  • All — they see and work every order on that page.

Can claim is the switch beside each row. With it on, they also see the orders nobody owns yet on that page and take one by opening it. It only works with Theirs or All — next to Off or View only it is dimmed — and it is always dimmed on Archive, because archived orders are never up for grabs. It is separate per page, so an agent can claim abandoned orders without claiming parcels on delivery.

Every order belongs to exactly one person. On Orders, Abandoned and Archive that is the agent it is assigned to; on the On delivery board it is the follow-up person (or the assigned agent while nobody follows the parcel yet). When an order is given to someone else, it is theirs alone — the previous agent no longer sees or works it, unless their page is set to All, and only gets it back if it is given back to them. An order an agent creates by hand is assigned to them straight away.

So a delivery agent can work every parcel on On delivery while only seeing their own orders on the Orders page, and an accountant can see everything without being able to change anything.

The role never overrides these settings. A role only picks the settings a new member starts with. Once saved, an Admin with Orders set to "Theirs" sees only their own orders, exactly like any other member. Only the store owner always sees everything.

Order actions sit under the page rows and apply on every page: Create orders, Send to courier (send the orders they work to a delivery company — this creates a real parcel, alone or in bulk), Reassign teammates' orders (give orders to someone else, take them away, or press "Assign waiting"), and Delete orders (only orders they can see). Each needs at least one order page turned on; Send to courier needs a page set to Theirs or All. Without it, the send button and "Upload for delivery" do not appear for them — they can still confirm orders for someone else to ship.

Before you save, the save bar lists exactly what changed — for example "Abandoned: Theirs, can claim" — so a setting changed by mistake shows up before it takes effect.

Someone appears in an assign list only if they can work that page (Theirs or All): the Orders page's list, the Abandoned list, and the follow-up list on On delivery each follow their own row.

Settings access is Admin-only. It cannot be granted to other roles, no matter how the rest of the permissions are set, because it is the group that includes billing and the store's own configuration.

The owner seat cannot be edited or removed. Permissions, limits and order routing apply to invited members only. There is exactly one owner.

Managers cannot raise their own access. A team member who can manage the team still cannot change their OWN role, permissions or status, and cannot give anyone a permission they do not hold themselves. Trying either is refused with a note saying so. Only the store owner (or another manager who has that permission) can do it. The owner is not limited this way.

Status. A member is pending (invited, not accepted), active, online right now, or suspended. Suspending keeps the person and their history but blocks them from signing in — the right move for someone who has left, or temporarily should not be working, since removing them entirely loses the record of what they did.

Access templates are reusable presets of your own, beyond the role defaults, for when you keep building the same unusual combination by hand. A template saved in one of your stores can be used in all of them.

Access per store. When you own several stores, the top of Access has a store list. The access shown underneath is for the store picked there, and its switch says whether the person can work in that store at all. Changes save to that store only.

Seats are limited by plan — owner included, across all your stores: 1 on Try, 2 on Starter, 6 on Growth, unlimited on Scale. A person in two of your stores is one seat. Inviting past your allowance, or switching a suspended member back on when every seat is taken, is refused with a note saying how many seats you have; upgrading or removing someone is what frees one. After a downgrade, the newest members are paused automatically until a seat frees up.

More in Team & chat

Still need help?

Ask the assistant from the search box in your dashboard. It answers from these same guides, in English, French or Arabic, and can make changes for you. Or write to us and a person will reply.