- Sector
- Our own support
- Company size
- The whole technical team
- Business lines
- Cybersecurity, Business solutions
- Solutions
- Odoo support, Managed cloud
Access that never switches off is a risk the client can't see
To resolve a ticket, ERP support has to get into the client's database. The easiest way is an admin user that the whole team shares and that is always open.
That way, nobody can say who made a change. And when someone leaves the team, you have to change passwords that hardly ever get changed.
It's the question every security audit ends up asking: who at your supplier can get into your data, and when.
- Each person with their own user
- No access left open once the task is over
- When someone leaves, their access is closed the same day
Named access, requested for each task
One user per person
Each technician has their own user in the client's ERP, with the permissions their role needs and nothing more. Everything they do is recorded under their name.
Off until it's needed
The user exists, but it is switched off. It is switched on for a specific task and switches itself off when the task ends.
Changes wait for the client's OK
Anything that changes something important in their system isn't done until the client approves it.
Many tickets, without logging in
A good share of problems are diagnosed by reading logs from outside, without touching the database.
Testing on anonymised data
We develop and test in a separate environment, with personal data anonymised. There is no copy of any client's database on the team's computers.
We put our own house in order first
The first step was to get rid of anything shared. Everyone on the team got their own user and password, and the shared user stopped being used for day-to-day work. That way, every action is recorded under the name of whoever does it.
Then came access per task. The technician requests it for a task, it gets approved, and when the task is done it closes without anyone having to remember to close it. For Odoo databases we built it as our own development, which we already use in our operations system.
Joiners and leavers follow a checklist. When someone joins the team they get only the access their role needs; when they leave, all of it is removed the same day.
Today this is how it works on every Odoo database we host for our clients.
The answer to ‘who gets in’ has to be a list of names
A client doesn't need to know how access is set up. They need to be able to ask who got into their system on a given day, and get a person and a reason as the answer.
That is only possible if nobody shares a user and no access is left open out of habit. The rest is detail about how we do it, and that we don't publish.
If you're worried about who gets into your ERP today, see how we handle Odoo support and managed cloud.
Do you know who can get into your ERP today?
Tell us how your support works and we'll work out together which access can go.