Team
Roles and permissions
Roles and permissions control who can see and do what in the admin. This is the single most important security tool in the system: it decides whether a colleague sees only orders, or the whole store including settings and customer data.
How access works
Every tool in the admin requires a specific permission (for example, products, orders, customers, settings, or the various team permissions). A role is a named bundle of permissions. You assign a role to a person, and they can use exactly the tools that role's permissions allow, and nothing else. The sidebar each colleague sees is filtered to match.
A full administrator has all permissions and sees everything. A warehouse colleague might have only the orders permission and see only Orders. If someone reports a section is missing, their role does not include that permission.
Managing roles
- Create a role for a kind of job (for example, "Support", "Warehouse", "Marketing").
- Grant it the permissions that job actually needs, and no more.
- Assign the role to the relevant people.
Tips
- Grant the least access that does the job. Give Support the customer and order permissions, not settings or backups. Smaller access means smaller mistakes and smaller risk.
- Use roles, not one-off grants. A handful of clear roles is far easier to manage than bespoke permissions per person, and it keeps access consistent as people join and move.
- Review periodically. When someone changes jobs or leaves, update or remove their role. Stale access is how data leaks.
- Protect the powerful permissions. Settings, backups, roles themselves, and customer data are the sensitive ones. Keep them to the few people who genuinely need them.