1. The big picture
Everything runs on one website and one database. Each person logs in with an e-mail and password; their role decides what they see.
/admin Β· Business app/operator Β· Business appβ¬ all connected to the same T Booking website & database β¬
| Role | Logs in at | Mobile app | Typical person |
|---|---|---|---|
| Super admin | /admin | T Booking Business | The owner of the booking website |
| Admin (and custom staff roles) | /admin | T Booking Business | Office staff, support, accounts |
| Operator | /operator | T Booking Business | A bus company, its manager, driver or conductor |
| Agent | /admin (limited) | T Booking Business | Ticket counter / travel agent who books for walk-in customers |
| Customer | /login β My account | T Booking | Passenger |
2. Super admin & admins
π Super admin
The account created by the installer. Can do everything and cannot be deleted or locked out by other admins. Only a super admin can make another user super admin.
Daily work
- Dashboard β bookings today, revenue, commission, trips, charts, popular routes and top operators.
- Operations β trips and recurring schedules, routes and stops, cities (import a whole country), manual bookings for phone customers.
- Fleet β buses, bus types, amenities and the drag & drop seat layout designer; bus operators and their commission rate.
- Customers β users, roles & permissions, reviews, messages, newsletter.
- Finance β payments, refunds, wallets, commission and operator payouts; approve bank transfers.
- Content & marketing β pages, blog, FAQ, banners, offers and coupons, SEO.
- Settings & system β branding, payment gateways, e-mail/SMS, languages, currencies, security, backups, updates.

π‘οΈ Admin and custom staff roles
An admin has all permissions by default, but cannot change the super admin. For other staff create your own roles (e.g. βSupportβ, βAccountsβ) in Admin β Roles & permissions and tick only what they need β the menu then shows only those pages, in the panel and in the Business app.

3. Bus operator
π Operator β a bus company
Every bus company gets its own operator panel at /operator and sees only its own buses, trips, bookings and money. The site owner earns a commission on each booking (per operator, set in Admin β Operators); the rest is paid out to the operator (Admin β Finance β Payouts).
In the operator panel
- Dashboard: bookings, revenue, rating, today's trips
- Fleet: view own buses (the admin adds buses and seat layouts)
- Trips: create trips, change status (delayed, cancelledβ¦), passenger manifest
- Bookings of their trips
- Reviews: read and reply
- Revenue and company profile
In the Business app (drivers & conductors)
- Today's trips, start / delay / complete a trip
- Passenger manifest with boarding ticks
- Scan QR tickets to check passengers in
- Share the bus GPS β passengers see the bus on the map
- Earnings


4. Agent
π§Ύ Agent β books tickets for walk-in customers
An agent works at a ticket counter or travel agency. They log in at /admin but see a short menu: Dashboard, Bookings and New booking. They book seats for a customer on any trip, take the payment at the counter and give the printed or e-mailed ticket. An agent sees only the bookings they made.
- New booking β choose the trip, pick the seats on the seat map, enter the passengers and the customer's contact details.
- Payment β choose Cash collected (confirmed at once), Bank transfer (awaiting approval) or Unpaid hold (24h). The customer receives the e-ticket with QR code.
- Bookings β find, print or resend their tickets later.

In the Business app an agent sees the trips and their bookings and can check passengers in with the QR scanner. What an agent may do can be changed in Admin β Roles & permissions β agent.
5. Customer (user)
π Customer β the passenger
Customers book on the website or in the T Booking app. They can book as a guest (only e-mail and phone needed) or create an account β with Google or Apple sign-in in the app.
Booking
- Search from β to β date, filter and sort
- Pick seats on the live seat map (booked and reserved seats cannot be chosen; ladies seats ask for confirmation)
- Enter passengers, apply a coupon, pay online or with the wallet
- Get the e-ticket with QR code by e-mail and in the app
My account
- My bookings: ticket PDF, cancel (refund to wallet), review
- Live bus tracking on the day of travel
- Saved passengers, wallet, refer & earn, notifications
- Profile, password, two-step login, delete account


6. Which mobile app for whom
π« T Booking passengers
For customers and guests. Anyone can install it from Google Play / the App Store.
π T Booking Business staff
For super admins, admins, operators and agents. There is no sign-up β accounts are created in the admin panel. Each person sees only what their role allows.
T Booking (passenger app)




T Booking Business (staff app)





What each role sees in the Business app:
| Business app screen | Super admin / Admin | Operator | Agent |
|---|---|---|---|
| Dashboard & revenue chart | β | β own company | β |
| Trips & passenger manifest | β all operators | β own trips | β view |
| Start / delay / complete / cancel a trip | β | β | β |
| Scan QR tickets & board passengers | β | β | β |
| Share bus GPS position | β | β | β |
| Bookings | β all | β own trips | β own bookings |
| Approve payment, resend, cancel & refund | β | β | β |
| Users (block / unblock) | β | β | β |
| Earnings | β | β | β |
Admins with a custom role see exactly the screens their permissions allow (e.g. a role with only βView bookingsβ sees trips, bookings and the scanner).
7. A booking from start to finish
- 1 Β· PlanThe admin (or the operator) adds buses, routes and trips β once, or with recurring schedules.
- 2 Β· BookA customer books on the website or in the app β or an agent books at the counter. Seats are held while paying, so nobody else can take them.
- 3 Β· PayOnline payment confirms the booking at once. A bank transfer stays βawaiting paymentβ (the seats stay reserved) until an admin approves it.
- 4 Β· TicketThe customer gets the e-ticket with QR code by e-mail and in the app. The operator sees the passenger in the manifest.
- 5 Β· Travel dayThe conductor starts the trip in the Business app and shares the bus GPS; passengers track the bus live. At boarding the QR ticket is scanned.
- 6 Β· AfterThe trip is completed; the customer can leave a review, which the operator can answer. If a booking is cancelled, the refund follows the cancellation rules and goes to the customer's wallet (or by the original payment method).
- 7 Β· MoneyThe site owner keeps the commission; the operator's balance is paid out from Admin β Finance β Payouts.
8. Permissions at a glance
| Can⦠| Super admin | Admin | Operator | Agent | Customer |
|---|---|---|---|---|---|
| Book tickets | β | β | β | β for customers | β |
| See all bookings | β | β | own trips | own bookings | own bookings |
| Manage trips & schedules | β | β | trips of own buses | β | β |
| Buses & seat layouts | β | β | view own buses | β | β |
| Refunds, payouts, finance | β | β | own revenue | β | own wallet |
| Users, roles, operators | β | β (not super admin) | β | β | β |
| Settings, languages, currencies | β | β | β | β | β |
| Security, backups, updates | β | β | β | β | β |
Admin and agent permissions are the defaults and can be changed per role in Admin β Roles & permissions.
9. Creating accounts & custom roles
π Operator
Admin β Operators β Add operator β fill in the company, and under Login an e-mail and password. That person logs in at /operator and in the Business app.
π§Ύ Agent / π‘οΈ Staff
Admin β Users β Add user β choose the role agent, admin or your own role.
π Customer
Customers sign up themselves (website or app), or you add them in Admin β Users with the role customer.
βοΈ Custom role
Admin β Roles & permissions β New role β tick the permissions β assign it to users.

After installing with demo data, change or delete the demo accounts (admin@, operator@, agent@, customer@tbooking.com) before going live.