Roles
Who is who in the Tulpar GO ecosystem from the partner's point of view.
Summary
| Role | Where they work | Main task |
|---|---|---|
| Super admin (platform) | Tulpar GO admin panel | Connects the partner, modules and cities; sees the whole network |
| Partner administrator | Partner cabinet | Runs the partner's work: tariffs, drivers, staff, finance |
| Dispatcher | Cabinet (limited access) | Takes calls, creates and handles orders |
| Driver | Mobile app (driver mode) | Accepts orders, completes rides / deliveries |
| Passenger | Mobile app (passenger mode) | Orders rides and deliveries |
Platform super admin
A Tulpar GO / X Labs employee. Partners usually deal with them when a city is connected, modules change, or for contract questions.
Does:
- creates the partner card and the first administrator;
- enables modules (taxi, delivery, intercity, etc.);
- sees a summary of the whole network (not just your data).
Does not do for the partner: daily dispatching, local tariffs and operational work with drivers in the city — that is the partner cabinet's job.
Partner administrator
The main partner account in the cabinet.
Does:
- sets up tariffs and packages;
- approves and blocks drivers;
- adds staff (dispatchers and others);
- reviews finance and platform invoices;
- works in Dispatch and Orders when needed.
Recommendation: one or two administrator accounts per partner; separate dispatcher accounts for shifts.
Dispatcher
A shift operator. Sees the operational sections (Dispatch, Orders, often Drivers), but usually does not change tariffs or financial settings.
Does:
- creates an order from a phone call or a request;
- assigns a driver manually or starts auto-search;
- cancels / reassigns an order according to the partner's rules;
- watches statuses on the map.
Detailed steps are in Dispatch.
Driver
Works only in the Tulpar GO mobile app (driver mode). Drivers do not sign in to the partner cabinet.
Does:
- goes online, accepts or skips order offers;
- marks ride statuses (arrived → on the way → complete);
- delivery and/or intercity, if those modules are connected.
The partner manages drivers in Drivers: application, class, block, packages.
Passenger
An app customer. Orders a taxi, delivery or intercity ride. The partner sees orders of passengers in its city / with its drivers in Orders, but does not manage passenger accounts the way the platform super admin does.
Access matrix (guideline)
| Section | Partner admin | Dispatcher | Driver | Passenger |
|---|---|---|---|---|
| Dispatch | yes | yes | — | — |
| Orders | yes | yes | own, in the app | own, in the app |
| Drivers | yes | view / limited | — | — |
| Tariffs / packages | yes | no | buys packages in the app | — |
| Partner finance | yes | no | balance/payouts in the app | pays in the app |
| Cabinet settings | yes | no | — | — |
The exact menu depends on the modules and the permissions granted by the partner administrator.