Administrator: full access, including user management, planning import, network settings and integrations.

Operator: all operations and resources (transport plan, vehicles, drivers, devices), without user management or network settings.

Regulator: day-to-day operations (trips, deviations, messages to drivers and passengers, alerts), without resources.

Reader: viewing of all operations, planning included, without changing anything.

Limited reader: like the Reader, without planning, driver messaging, device details or trip list export. It keeps the trip history and reports.

External reader: for someone outside your company (transport authority, partner): map, routes, passenger messages and the trip list from 7 days before to 7 days after today, without details or sensitive data.

For whom: the person or people responsible for Pysae on the network, usually the operations manager or the tool referent.

What they can do: everything the Operator does, plus add and edit users (“Resources” > “Users”), import a planning, manage depots and subcontracting, edit stop information, set the “Network settings” (punctuality, driver app, passenger counting, API keys…) and the “Integrations” (onboard equipment), and choose notification recipients.

Good to know: an administrator can only give a user teams they belong to themselves, and cannot change their own role.

For whom: people who run operations and manage the network's resources.

What they can do: all operations: map, trips with their full history, cancellations, deviations, comments, messages to drivers and passengers, alerts, sign-on and sign-off, reports, viewing the planning. They also manage “Resources”: transport plan (GTFS import and publication), vehicles, drivers, devices. They can export the trip list, drivers and vehicles.

What they cannot do: manage users (they see the list but cannot change it), import a planning, open the “Network settings” and “Integrations”.

For whom: control room regulators who follow the service in real time.

What they can do: the same day-to-day operations as the Operator: map, trips, cancellations, deviations, comments, messages to drivers and passengers, emergency alerts, sign-on and sign-off, reports, viewing the planning, exporting the trip list.

What they cannot do: open “Resources” (transport plan, vehicles, drivers, devices, users), “Notification settings”, network settings and integrations.

For whom: people who view without acting: sales agents informing passengers, transport authority staff, management.

What they can do: view the map, trips with their full history and details (vehicle, driver, mileage), the dashboard, stops, deviations, reports, the planning, messages exchanged with drivers and device details. They can export the trip list.

What they cannot do: create or change anything: no cancellation, deviation, comment, message to drivers or passengers.

For whom: people who need to follow operations and statistics, without access to driver communications or service organisation.

What they can do: like the Reader: map, trips with their full history (13 months) and details, dashboard, stops, deviations, reports, passenger messages, all view only.

What they cannot do: see the planning, driver messaging and device details, export the trip list, and of course change anything.

For whom: someone outside your company (transport authority, partner, contractor) you want to show the service to without giving access to sensitive data.

What they can do: view the “Map” with vehicles in real time, “Routes”, “Passenger messages” and the passenger display, and the “Trips” list from 7 days before to 7 days after today. Depending on your network's options, they also see the delay grid and onboard screens, view only.

What they cannot do: open trip details, see the vehicle, driver, device or mileage of a trip, go back more than 7 days, export, view the dashboard, stops, deviations or reports, create or edit a passenger message.

With teams: if you give them a team (for example a subcontractor), they only see that team's vehicles and trips.

Teams: on top of the role, an administrator can limit a user to one or more teams. The user then only sees the trips, vehicles and devices of those teams.

Network options: some pages only appear if the feature is enabled on your network (planning, deviations, delay grid, onboard screens, sound announcements, on-demand routes, SIRI and GTFS-RT feeds, emergency alerts…). An authorised role may therefore not see the page.

The Driver and Technical account roles give no access to the supervision interface: the first is for the Pysae Driver app, the second for automated exchanges (API).