Get demo access

Platform · Access and permissions

Companies on one vehicle cannot see each other.

Every request is checked three ways: may this person do it, can the vehicle do it, and was it sold to this organisation. Access is granted per vehicle and down to single data fields, so a workshop reads the battery but not the position, and a dealer serving three brands never sees another dealer's vehicles.

See it as

OEM Suite · vehicle access · demo data

01Three checks

Three questions, on every request.

Asked in this order. If one answer is no, nothing else is looked at.

A requestDemo Workshop Lucerne reads the battery voltage of one LiveWire ONE

  1. 1Permission

    May this person do it?

    The role of this person, in this organisation, on this vehicle. Resolved per request, not at login.

    No: it stops here

  2. 2Capability

    Can the vehicle do it?

    What the vehicle and its hardware support, set per vehicle type. A function it cannot support is not offered.

    No: it stops here

  3. 3Entitlement

    Was it sold to them?

    What an organisation's plan includes switches its functions on. The free tier still covers serving your customers.

    No: it stops here

Answered11.8 V, with the permission that let it through

02Roles

Seven roles, given per vehicle.

Per vehicle, not per account. Owner, manufacturer and maintainer are protected and cannot be changed, even by the owner.

Personal roles

  • UserUses the vehicle like the owner, without managing access.
  • Read-onlySees, changes nothing.
  • Read-only, no detailsSees the vehicle, not its detail.
  • Current status onlyThe position and data right now, no history.

A person or an organisation

Owner

Everything, including who else gets access. A rider owns their motorcycle, a rental company its fleet.

Protected

Reserved for organisations

  • ManufacturerYour own view of every vehicle you built.Protected
  • MaintainerOnly what maintenance needs. Never anything personal: not where the vehicle is, not where it has been.Protected

Every grant has a start and an end.

A role is given from a date, until a date, or open-ended. Before and after, the vehicle is closed to them, without anyone having to remember.

  1. Alex MeierOwner

    ActiveSince 2 Sep 2025

  2. Talmark MotorradRead-only

    Ended23 Dec 2025 to 21 Jun 2026

  3. Demo Workshop LucerneMaintainer

    Active21 Sep to 24 Oct 2026, the repair

  4. Sam MeierCurrent status only

    Scheduled1 to 8 Dec 2026, a week's loan

LiveWire ONE · four grants · demo data

Fixed roles per vehicle, plus the roles your organisation defines. Underneath, more than 200 permissions decide what a role may do, and 1,589 more decide, field by field, which data it may read.

03Field level

The workshop sees the fault, not the address.

One LiveWire ONE, as four roles see it. Every card has the same rows. The role decides which of them arrive.

LiveWire ONEDriver app

Owner

Alex Meier

Owner

Where it is
46.004° N, 8.951° E
Owner
Alex Meier
Fault
ERR-002 · Low battery voltage
Charge
62 % · 11.8 V
Trip log
126 trips, mapped
Service
First service · 12 Aug

LiveWire ONEOEM Suite

Manufacturer

Coride Motors

Manufacturer

Where it is
Not visible in this role
Owner
Alex Meier
Fault
ERR-002 · Low battery voltage
Charge
62 % · 11.8 V
Trip log
126 trips, distance only
Service
First service · 12 Aug

LiveWire ONEPartner Hub

Workshop

Demo Workshop Lucerne

Maintainer

Where it is
Not visible in this role
Owner
Alex Meier
Fault
ERR-002 · Low battery voltage
Charge
62 % · 11.8 V
Trip log
Not visible in this role
Service
First service · 12 Aug

LiveWire ONEPartner Hub

Dealer

Alpine Moto Center

Sales, its own role

Where it is
Not visible in this role
Owner
Alex Meier
Fault
ERR-002 · Low battery voltage
Charge
62 % · 11.8 V
Trip log
Not visible in this role
Service
Not visible in this role

LiveWire ONE · four roles · demo data

The workshop holds maintainer: only what maintenance needs, never where the vehicle is or has been. The dealer only sells, so it holds a role of its own without the service history. Every field has its own permission, 1,589 of them.

And in time

Which part of the vehicle's past they may see.

Every grant also carries a window on the vehicle's history, separate from how long the access lasts. A new owner gets the vehicle's whole service and error history, but its readings, trips and positions only from the day they bought it.

Service historyThe whole book, also from before the sale.

ErrorsEvery error the vehicle ever had.

Readings and eventsOnly from the day they bought it.

Trips and positionsOnly whole trips after the sale. One across it shows to no one.

We enforce permissions at the platform level across every interface and API request. Anything you plug into it, whether your own service, a partner app or an AI agent, sees only what those rules permit.

04One grant

A mechanic gets a vehicle, then loses it.

One grant from start to end, on Demo Motorcycle 1. Nobody has to clean up after it.

  1. Granted

    09:00 · Dealer → mechanic

    Gives the workshop's mechanic Demo Motorcycle 1 as maintainer. The vehicle's history records it.

    MaintainerDemo Motorcycle 1

    Given by Alpine Moto Center

  2. In use

    09:01 · Mechanic

    Opens the error code and the service history. The position fields never leave the server.

    Error codeE-104

    Service history3 entries

    Position

  3. Removed

    10:30 · Dealer

    Removes the access. The mechanic's open live stream is re-scoped at once, not at the next login.

    Live streamRe-scoped

    At once, still signed in

  4. On record

    After · You

    Both entries stay on the vehicle's history: who granted, who removed, on behalf of which organisation.

    09:00Access given, by Alpine Moto Center

    10:30Access removed, by Alpine Moto Center

On every answerThe API says which permission let it through, and whether it came from the person or their organisation.

05Sharing

Share anything, only with the right people.

You can share anything attached to a vehicle, including documents, checklists, maintenance plans, news and push messages, simply by picking who gets it. The platform makes sure nobody else does.

06Questions

Asked by security teams.

Can one dealer work for several of our brands, and for other manufacturers?

Yes. A dealer can be a partner of many manufacturers at once, and access is decided per vehicle. It sees each brand's vehicles that were granted to it, and never another dealer's.

What happens when we revoke access?

Access ends at once. An open live stream is cut back to what the person may still see, without a new login. Invitation and consent links are single-use and expire after seven days.

Is there an audit trail?

Every access a person is given on a vehicle, and every removal, is written to that vehicle's history, with who did it and on behalf of which organisation. Every API response also states which permission allowed it.

Can we define our own roles?

Yes. Organisations can create their own roles on top of the fixed ones. The platform checks permissions, never role names, so a role of yours behaves like one of ours.

What if someone tries to take over a vehicle that already has an owner?

The current owner gets an email, in English, German or French, and decides within seven days whether to accept or decline.

Explore the demo.

Talk to our engineers →