Network Store Basics
Who can see and do what in the Network Store
How access is decided, why a tribe manager can buy without any admin role, and what to check when someone cannot see the store.
Last updated September 2, 2026
Access to a store is decided by two things: which organisation the person belongs to, and what access that organisation has been given to the store.
Shopping and administering are different
This is the part that surprises people. Shopping does not require an admin role. A tribe manager who holds no role in your organisation can still open the storefront and buy, because the gate is "may this person shop for this organisation?" rather than "are they an administrator?".
Administering the store is the opposite: it requires membership of an organisation that holds Owner or Manager access. Buyer-only access never opens an admin screen, however senior the person is.
What each level opens
| Buyer | Manager | Owner | |
|---|---|---|---|
| Shop the storefront | Yes | Yes | Yes |
| See their own orders | Yes | Yes | Yes |
| Products, orders, subscriptions, receivables | No | Yes | Yes |
| Store settings | No | No | Yes |
| Create or delete a store | No | No | Yes |
When someone cannot see the store
- Is their organisation shared into the store at all? No sharing, no access.
- Are they attached to that organisation in Gorilla Dash? A person with no link to it cannot shop for it.
- If they can see the store but not a particular product, that is the product's audience, not their permissions.
- If they can see the store but no admin screens, they have Buyer access — that is working as intended.
Granting access well
- Default to Buyer. It is what almost everyone needs.
- Give Manager only where an organisation genuinely runs part of the store — it exposes every customer and balance in it.
- Keep Owner to your own organisation.
- Review sharing when brands join or leave the network. Removing access does not stop their subscriptions billing.