Ecommerce team permissions stop being theoretical the moment you make your first hire. Suddenly someone else can open your orders, your customer list and, unless you plan for it, your margins. Most access problems in small online stores are not break-ins. They are a helpful employee who edits the wrong product, deletes a customer by mistake, or sees supplier costs they were never meant to see. This guide walks through a practical permission model for a growing store, from a two-person shop to a team with a warehouse, a bookkeeper and a sales desk, and shows how the team roles feature in StoreChart maps to each stage.
Ecommerce team permissions: why they matter
Without clear permissions, every login is effectively an owner login. Anyone can change prices, cancel orders, or export the customer list. And when something goes wrong, there is no structure that explains who was supposed to be able to do it.
A permission model gives each person a defined lane. It protects the business, and it also protects the employee from being blamed for access they never asked for.
The main things worth protecting:
- Cost and margin data. Product costs, profit per order and expenses tell a competitor or a departing employee exactly how much room you have on price.
- Customer data. Names, phone numbers and addresses belong with the people who serve customers, not with everyone on payroll.
- Destructive actions. Deleting products, editing orders and changing stock levels should sit with people who own those processes.
- Billing and the team itself. Who pays for the account and who can add or remove colleagues should stay with the owner.
Team roles: six ready-made roles
StoreChart separates the account owner from roles. Everyone other than the owner gets one of six roles:
- Account owner: always has full access, and is the only person who can invite, edit or remove members and change the subscription.
- A classic ladder: admin, store manager and employee.
- Job archetypes: accountant, warehouse and sales rep. They cover common "sideways" needs, such as a bookkeeper who needs margins but must never touch stock.
| Role | Typical person | Can work with | Does not see |
|---|---|---|---|
| Admin | Co-founder, operations lead | Everything, including stores, expenses and profitability | Team management (owner only) |
| Store manager | Shift or shop manager | Orders, customers, inventory, products, charges, tasks | Profitability, expenses, store settings |
| Employee | New hire, support agent | Read-only orders, customers, inventory and products; tasks | Profitability, analytics, charges, settings |
| Accountant | Bookkeeper, finance manager | Profitability, expenses, charges, analytics | Editing orders, stock or customers |
| Warehouse | Picker, logistics | Orders, inventory and products (edit) | Customer book and WhatsApp inbox, costs, charges |
| Sales rep | Sales or phone desk | Orders and customers (edit), products and stock (view) | Profitability, analytics, charges, expenses |
One detail matters most in practice: hiding margins is enforced on the server. For roles without profitability access, cost and margin fields are removed from the data before it reaches the browser, not just hidden in the table.
Least privilege
Start every new hire on the narrowest role that lets them do the job, then widen access when a real need appears. Removing access later always feels like a demotion; adding it feels like trust.
Custom access per member
Sometimes a role is almost right: your sales rep also handles payment pages, or your warehouse lead should not see the tasks board. For these cases the owner can open the member's access editor and switch on custom access.
Custom access works at two levels:
- Pages. The editor lists every page in the app. You can add pages the role does not include or remove pages it does, and each row shows whether its state comes from the role or from your change, so the screen still makes sense six months later.
- Hubs. You can limit a member to specific hubs, for example Commerce but not Communication. A hub restriction keeps working when new pages are added to that hub.
Three things to know about the editor:
- Pages outside your plan: appear locked with an upgrade path rather than disappearing, so "why can't they see this?" has a visible answer.
- Server-side checks: custom access decides which pages a member can open, and it is checked by the API as well as the menu.
- Actions on a page: what they can change on those pages still follows their role.
Team invitations and seats
Only the owner can invite members. This is how an invitation works:
- What is sent: an invitation to an email address with a role and, optionally, custom access that applies the moment the person accepts.
- Validity: the link is valid for seven days.
- Resending: creates a new link and kills the previous one. That matters when an email was forwarded to the wrong person.
- Cancelling: you can cancel a pending invitation at any time.
Every active member and every pending invitation occupies a seat, and the number of seats depends on your plan (see pricing). Counting pending invitations prevents the classic workaround of sending twenty invites and hoping they all fit.
When someone leaves, removing them from the team also cancels any pending invitation for their email, so an old link cannot bring them back. Nobody can edit their own role or access, and the owner's account cannot be removed from the team screen.
Do permissions apply per store?
No, and it is worth knowing before you plan your structure. Roles and custom access apply to the whole account, including every store you connect through multi-store management. A store manager sees the orders of all your stores, not just one.
If two brands must never see each other's customers or numbers, the clean solution is separate StoreChart accounts. Trying to fence them off with permissions will not work.
Role setup by team size
Two examples of how the same six roles fit a small shop and a larger operation.
Example: a 5-person store
Say a store has an owner, a partner, two people on customer service and one person packing orders. A workable setup:
- The partner: admin.
- Customer service: the employee role. They can look up any order or customer to answer a question, but cannot edit prices or delete records.
- The packer: the warehouse role, which shows orders and stock but hides the customer book and every cost figure.
- The bookkeeper: if they log in once a month, give them the accountant role instead of sharing the owner's login.
Example: a 30-person operation
Now imagine a business with several brands, a sales desk and a small finance team:
- Store managers: run day-to-day operations for orders and stock without seeing profitability.
- Sales reps: work with customers and orders without seeing costs.
- The finance team: uses the accountant role, the only role besides admin that sees profitability.
- Admins: reserved for two or three people.
- Exceptions: custom access, for example for a senior sales rep who also manages payment pages.
5 habits for managing permissions
A good role structure decays without maintenance. These habits keep it honest:
- Review access every quarter. Open the team screen, check each person's role against what they actually do today, and remove anyone who has left.
- One person, one login. Shared accounts make it impossible to reason about who could have done what. Seats are cheaper than confusion.
- Turn on two-factor authentication. Each member enrols an authenticator app in their own profile. Make it a rule for admins and accountants.
- Don't hand out admin to save time. Admin sees expenses, profitability and store settings. If someone needs one extra page, use custom access instead.
- Check the role before you invite. It is easier to invite with the right role than to fix it after the person has already explored the app.
Summary: permissions protect people too
A clear permission model lets each team member work confidently inside their lane. It keeps margins and customer data with the people who need them, and leaves the owner in control of billing and the team itself. Start with the closest of the six roles, adjust with custom access where a role does not fit, and revisit the setup every quarter.
Frequently asked questions
Who can invite or remove team members?
Only the account owner. Admins get almost everything else, but user management is reserved for the owner, and no member can change their own role, status, or access. The owner's own account cannot be removed from the team screen.
Can I restrict an employee to a single store?
Not today. Roles and custom access apply across the whole account, including every connected store. You can limit which pages and hubs a member reaches, but not which store's data they see on those pages. Brands that must stay fully separate belong in separate accounts.
How long is an invitation link valid?
Seven days. Resending an invitation issues a new link and immediately invalidates the old one, so a forwarded or leaked email stops working. Pending invitations count toward your plan's seat limit until they are accepted or cancelled.
Is there two-factor authentication for team members?
Yes. Each member can enrol an authenticator app from their own profile settings and receives recovery codes. Enrolment is voluntary, but once a member enrols, sign-in and sensitive actions require the code, so ask everyone with admin or accounting access to turn it on.
