Blog

Who Needs Pump User Permissions in Their Fleet?

A fuel tank can be physically secure and still leak money. The weak point is often not the tank, hose or pump – it is the question of who can dispense, when they can do it, and whether the transaction can be proved afterwards. That is who needs pump user permissions: any operation where fuel or fluids have value, access is shared, and a missing litre creates a real cost or compliance problem.

For a small fleet, the issue may be a few drivers accessing one yard tank outside normal hours. For a multi-site operator, it may be hundreds of drivers, contractors and maintenance staff across fixed tanks and mobile fuel units. The scale changes, but the requirement does not: every dispense should be authorised, attributable and available for review.

Who needs pump user permissions most?

Pump user permissions are not reserved for large fleets with complex security teams. They are most valuable where an organisation needs to separate legitimate access from assumed access. A key, shared PIN, handwritten logbook or open pump asks managers to trust a process that cannot reliably answer who dispensed what.

Fleet operators are an obvious fit. Lorries, vans, plant and service vehicles can consume substantial volumes across a week, and even a small variance between purchased fuel, tank stock and vehicle use becomes difficult to explain. Assigning permissions to named users creates a clear link between the person at the pump, the vehicle or asset being fuelled, the product dispensed and the time of the transaction.

Mobile fuelling businesses also need strong permissions. A mobile fuel lorry may serve several customer sites in a day, with different products, drivers and delivery requirements. If the same person can access every pump, every tank and every client allocation without controls, a mistake or unauthorised dispense can be hard to isolate. Role-based permissions make it possible to grant access for the work required without opening the entire operation.

Airports, municipal yards, construction operations, agricultural businesses and private depots face similar exposure. They may dispense diesel, petrol, DEF, lubricants, hydraulic oil or other fluids. The product changes, but accountability remains the operating standard.

Fleets with high fuel spend or frequent dispensing

The more often a pump is used, the less practical manual controls become. A supervisor cannot stand beside every dispense, and a paper sheet does not prevent an unauthorised transaction. Organisations with frequent fuelling need the ability to authorise a user before product flows, while capturing the record automatically rather than reconstructing it at month end.

This matters especially where fuel is dispensed outside office hours. Night shifts, weekend operations and remote depots are not inherently risky, but they require controls that operate without a manager being present. A permission system can allow an approved driver to fuel a vehicle at 04:30 while keeping everyone else out.

Multi-site operations that need one control point

Multiple depots create a familiar problem: every site develops its own workaround. One location uses keys, another has a keypad, and a third relies on a caretaker. Over time, permissions become inconsistent, former employees retain access, and finance receives records in different formats.

Centralised user permissions give fleet and operations managers a single way to approve, amend or remove access. A driver transferred to another depot can receive the right access without changing hardware at each site. When someone leaves, access can be removed immediately rather than waiting for keys, fobs or codes to be returned.

This is particularly useful for organisations with seasonal staff, agency drivers or contractors. These users may need limited access for a defined period, not permanent entry to every fuel point. Good permissions reflect that reality.

What pump user permissions should control

The right setup is not simply a digital version of a shared code. It should match access to operational responsibility. A driver needs a different level of access from a fuel manager, and a contractor should not automatically have the same rights as a permanent employee.

At a minimum, an organisation should be able to control four things:

• which named users can dispense;
• which pump, tank, site or mobile unit they may use;
• which vehicles, assets or jobs can be associated with a transaction; and
• when access begins and ends, including prompt removal when a role changes.

Depending on the operation, permissions may also limit product type, transaction volume or the use of specific equipment. These controls should be proportionate. Restricting every driver to one exact pump may create unnecessary delays at a busy depot. Giving every user unrestricted access because it is convenient creates a different and more expensive problem. The practical answer is to define clear roles and review exceptions rather than applying one rule to everyone.

When a manual process is no longer enough

A manual logbook may appear adequate while the team is small and the same people work the same shift. Its limits become obvious when there is a discrepancy. Handwriting is unclear, entries are missed, vehicle registrations are recorded incorrectly and there is no reliable proof that the person signing the sheet was the person dispensing.

Shared keys and keypad codes have the same weakness. They control entry only loosely, not identity. Once a code is passed on, there is no useful audit trail. Changing it can also disrupt legitimate users, which is why many sites postpone the task and leave old access in place.

Pump user permissions are needed when any of the following questions takes too long to answer: Who accessed the pump? Was that person authorised? Which asset received the fuel? Does the quantity match expected use? Can the transaction be reconciled to inventory and cost records?

If those answers currently depend on asking staff, searching paperwork or estimating tank levels, the business has an accountability gap. That does not mean every variance is theft. It may be an incorrect asset selection, a delivery issue, a leak, idling, poor data or a faulty meter. But without dependable transaction data, the cause remains speculation.

Permissions protect more than fuel

The financial case for controlled dispensing is straightforward, but the operational value goes further. Authorised access protects equipment and helps enforce safe working practices. Pumps and fluid systems should be used by people who understand the product, the equipment and the site rules. This is relevant for hazardous fluids, high-value lubricants and any operation where an incorrect dispense can damage an asset or contaminate a tank.

Permissions also improve the quality of fleet reporting. When a transaction is tied to a known user and asset at the point of dispense, managers receive data that is more useful for reconciliation, budgeting and investigations. They can identify unusual patterns sooner, such as repeated fuelling of one vehicle, activity at unusual times or consumption that does not align with distance travelled.

The benefit is not surveillance for its own sake. It is a defensible record that protects honest drivers and gives managers evidence when something needs attention.

Building a permission model that people will use

The best system is simple enough for the driver at the pump and detailed enough for the manager reviewing spend. Start by mapping the real roles in the operation: drivers, plant operators, technicians, site supervisors, fuel attendants and administrators. Then decide what each role genuinely needs to access.

Avoid creating permissions around informal habits such as “everyone at this depot knows the code”. Instead, define the approved user, the relevant site or unit, and the assets or products involved. Set a process for new starters, temporary access and leavers. A permission model only stays secure if user records are maintained as actively as vehicle records.

Cloud-connected access control is valuable here because changes do not require a visit to every pump. With FluidSecure™ from Manage Every Drop, authorised users can be managed through a smartphone-based system while transactions are recorded in the cloud at the time of dispensing. That reduces the hardware and maintenance burden associated with traditional pedestal-based systems, without sacrificing the evidence needed for control and reconciliation.

Before selecting any approach, check how it handles poor mobile coverage, emergency access, temporary staff and mobile fuel units. A system should support real operations, not force crews into workarounds. It should also make reporting clear enough that finance, fleet and site teams can work from the same transaction record.

A pump should not rely on a promise that only the right people will use it. Give authorised people quick access, remove access when it is no longer justified, and make every dispense visible. That is how a fuel point becomes a controlled business asset rather than an open-ended operating cost.