Granular, not three tiers
Permissions are per screen and per action, so a salesperson can write offers without seeing margins.
Team & control
Give people exactly the reach they need
Fifty-seven individual permissions, per user. Every change recorded with who made it, when, and what the value was before.
| When | Who | What | Entity |
|---|---|---|---|
| 09:41 | Dana | update | DiscountRule |
| 09:38 | Leo | create | Quote |
| 09:12 | Dana | login | User |
Nothing is anonymous
Every meaningful change is attributed. “Who changed this price” has an answer with a timestamp.
Your branding and language
Per instance and per user: colours, logo and interface language, including Romanian.
Your own instance, not a shared tenant
Each customer gets a separate deployment with its own database, its own users and its own backups. Nobody else’s data is in the same box as yours.
- Separate database per customer
- Your own subdomain with HTTPS
- Sessions revocable, passwords forced to change on first use
1
Own database
2
Own subdomain
3
Own backups
4
Own users
Control, in detail
- Fifty-seven individual permissions, set per user
- Per screen and per action, not three fixed tiers
- Roles as a starting point, overridden per person
- Separate permissions for preparing and for publishing
- The AI assistant gated per user, and per action within it
- An audit trail with who, what, when and the value before
- Sessions you can revoke immediately
- A forced password change on first sign-in
- Per-user interface language — Romanian, English, German, French
- Per-instance branding: logo, colours, document wording
- Your own document numbering and order reference prefix
- Daily backups of your own database
In practice
Bringing a new salesperson in on Monday
Five minutes, and they can do their job and nothing else.
- Create the account; they must set their own password on first sign-in.
- Start from the sales role, then tick or untick individual permissions.
- Decide whether they may use the assistant at all — it is off unless granted.
- If they may, tick which actions it will perform for them. Drafting offers, perhaps; publishing prices, perhaps not.
- Everything they do from then on is attributed, with the before value kept.
| Area | Sales | Admin |
|---|---|---|
| Write offers | yes | yes |
| See margins | no | yes |
| Publish discounts | no | yes |
| Use the assistant | ask | yes |
Questions about this
Can I hide prices or margins from some people?
Yes. Permissions are per screen, so a salesperson can write offers without seeing cost or margin anywhere.
What is in the audit trail?
Who acted, what they changed, the entity, the time, and the value before the change. It covers what happens in this tool; changes made in PrestaShop itself stay in PrestaShop.
Who can see the audit trail?
Whoever you give the permission to. It is not on by default for non-administrators.
See it against your own catalogue
Tell us about your shop and we will set up an instance for you. You will be looking at your own products, not a demo dataset.
Request access
No card. No obligation.