Overview
A user is a person who logs into your system with a login and password. Each user:
- Belongs to a role (which determines their permissions — what they can see and do).
- Is linked (in multi-company setups) to one or more companies (which determines what data they see).
- Can be restricted to specific shops (on certain configurations).
- Has personal settings: avatar, language, notification management, access to the media manager.
You manage users from Administration > Users.
List
Filters
- Search by name or email.
- Interface (if the WTB module is enabled): ERP (your staff) or Want to buy (your WTB suppliers who have an account on the dedicated portal).
Columns shown
- Avatar — The user's photo.
- Name — Full name.
- Email — Email address.
- Created on — Account creation date.
- Role — Permission profile assigned.
- Interface (if WTB is enabled) — ERP or Want to buy.
- Company/companies (if multi-company) — List of companies the user has visibility on (or "All companies" if there is no restriction).
- Actions — Impersonate (super-admin only), Edit, Delete.
Create a user
New button: opens the full form.
"User information" panel
| Field | Description |
|---|---|
| Name | Full name of the user. Required. |
| Email address | Login email. Must be unique in the database. Required. |
| Password | Initial password. Required when creating. When editing, leave blank to keep the same password. |
| Confirm password | Re-enter the password identically to confirm. |
| Language | Display language of the interface (if several languages are enabled on your tenant). |
"Access" panel
| Field | Description |
|---|---|
| User role | Selection from the configured roles (see the Roles section). Determines the user's permissions. |
| Company visibility (multi-company) | Multiple selection. Restricts the user's visibility to the companies checked. If nothing is selected, the user sees all companies. |
| Shop visibility (specific configurations) | Multiple selection of shops. If no shop is set, the user has visibility on all shops. |
Good to know — Restriction by company
If a user only has access to company A, they will not see the stock, orders, shipments, invoices, and other operations linked to company B. This is a very useful partitioning mechanism for organizations with several legal entities, each with its own dedicated team.
"Avatar" panel
Upload an image (profile picture). Appears in lists and in the navigation bar to identify the user.
"Media manager" panel (super-admin only)
| Field | Description |
|---|---|
| Restrict media manager access to a folder | Toggle. If enabled, the user only sees one specific folder of the media library (not the whole media library). |
| Create a folder for this user? (on creation) | If enabled, a folder is automatically created under their name in the media library. |
| User's folder | Selection of the folder the user is restricted to (if the Create a folder option is disabled). |
Useful for keeping content editors separate: a community manager can upload images without seeing or editing other people's.
"Notifications" panel
- This user can receive email notifications — Toggle. If enabled, the user receives notification emails (export completed, sale received, stock alert…).
"Linked third party" panel (if applicable)
When editing a front (e-commerce frontend) or WTB user, a panel shows the third party the account is linked to (CRM customer or WTB supplier). Edit customer button to quickly navigate to the third party's record.
Save buttons
- Create — Creates the user and stays on the record.
- Create and return — Creates the user and goes back to the list.
- Create and new — Creates the user and opens a blank form.
Impersonate (super-admin mode)
On the list, the Impersonate icon on a row (visible only to super-administrators, for ERP users) lets you log in as this user without knowing their password. Very useful for support and troubleshooting — you see the system exactly as the user sees it, with their permissions and restrictions.
Once in impersonate mode, an Exit impersonate button appears to return to your own account.
Caution — Impersonate should remain a one-off diagnostic tool. All actions performed in impersonate mode will appear in the Activity log as performed by the impersonated user — be careful with any changes made in this mode.
Delete a user
Delete action on the list: confirmation, then permanent deletion. The user can no longer log in; the operations they created remain in the database under their historical name.
Good to know — You cannot delete yourself. And deleting a super-administrator is locked, to avoid ending up with no access to the configuration.